◆ Microsoft SQL Server

Implement workflows using SQL Server Agent

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 taskCreate a new database agent job named 'DailySalesDataExport' that runs the stored procedure…+
Create a new database agent job named 'DailySalesDataExport' that runs the stored procedure 'ExportSalesDataToCSV' every day at 2 AM. I need this data ready for the sales team by morning.
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 acceptBefore I set up the new job to process customer feedback, make sure it has proper error…+
Before I set up the new job to process customer feedback, make sure it has proper error handling to log any failures to our central error table, and notify me via email if it fails. I need to know if something goes wrong without constantly checking it.
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 new job that loads data into the analytics warehouse finished successfully, but the data…+
The new job that loads data into the analytics warehouse finished successfully, but the data isn't showing up in the reports.
The new job that loads data into the analytics warehouse finished successfully, but the data isn't showing up in the reports. The logs say 'success', but the analytics team is saying their dashboards are empty. I'm afraid I missed a step in the data pipeline that isn't captured in the job itself. What's the most common reason a job reports success but doesn't deliver the expected outcome, and how can I quickly verify the data actually landed where it should have?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself manually restarting or fixing jobs that failed due to simple, preventable…+
I often find myself manually restarting or fixing jobs that failed due to simple, preventable issues.
I often find myself manually restarting or fixing jobs that failed due to simple, preventable issues like network timeouts or temporary resource unavailability. What habit should I change in how I design and implement new database agent jobs to build in more resilience and self-correction, reducing my manual intervention time?
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.