◆ Microsoft SQL Server

Automate SQL queries to run daily

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up an automated job to run the 'DailySalesSummary' query at 6 AM every weekday. It needs to…+
Set up an automated job to run the 'DailySalesSummary' query at 6 AM every weekday. It needs to save the results as a CSV file to the shared 'Reports' folder.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptI need to automate the 'DailySalesSummary' query to run every morning. Before I schedule it,…+
I need to automate the 'DailySalesSummary' query to run every morning. Before I schedule it, ensure it's robust enough to handle potential data inconsistencies or large result sets, and suggest a good way to notify me if it fails or returns unexpected results, so I don't miss anything important.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe automated daily sales report for Mark in finance just ran, and it's showing zero sales for…+
The automated daily sales report is showing zero sales, but I know that's wrong.
The automated daily sales report for Mark in finance just ran, and it's showing zero sales for yesterday, which I know is incorrect based on our POS system. Mark is expecting accurate numbers by 8 AM. I'm worried the query itself is flawed or the data source had an issue, but I don't have time to deep-dive into the entire database. What's the most likely reason for this discrepancy, and what's the quickest way to get him the correct numbers without causing further delays?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly chasing down issues with automated SQL queries that fail silently or produce…+
I frequently get urgent requests to fix or re-run automated reports that have failed or produced bad data.
I'm constantly chasing down issues with automated SQL queries that fail silently or produce incorrect data, leading to last-minute scrambles for stakeholders like Sarah in marketing. I need to change my habit for setting up these automations to include better validation and error handling from the start, so I can trust the output and reduce my reactive workload.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Microsoft SQL Server's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.