◆ Microsoft SQL Server

Configure schedule for SQL Server Agent job

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 a database agent job to run the 'Cleanup_Old_Data' stored procedure at 2 AM every day,…+
Set up a database agent job to run the 'Cleanup_Old_Data' stored procedure at 2 AM every day, starting tomorrow, June 1st, and log any failures to the 'DBA_Alerts' table.
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 put this new nightly data cleanup job into production, make sure it won't clash with…+
Before I put this new nightly data cleanup job into production, make sure it won't clash with the 1 AM backup window or the 3 AM index rebuild. I need to know if it's going to cause any performance spikes during those critical times or if it can be safely run without impacting our daily operations.
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 'Sales_Performance_Report' job failed again last night at 1:30 AM, and now the sales team…+
The new nightly report job failed again last night, and I'm getting heat from the sales team.
The 'Sales_Performance_Report' job failed again last night at 1:30 AM, and now the sales team is hounding me for missing data. It's supposed to run after the ETL finishes, but the ETL logs show it completed on time. I'm afraid to restart it without knowing why it failed, especially since it affects executive dashboards. Did the ETL actually finish everything it needed to, or did something else block the report from running? What's the best way to get this report out to them without causing further issues?
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 reacting to failed automated jobs that impact critical business reports,…+
I keep getting pulled into urgent report failures that could have been prevented.
I'm constantly reacting to failed automated jobs that impact critical business reports, especially on Monday mornings. It feels like I'm always troubleshooting after the fact. What habit should I change to proactively identify potential job failures or performance bottlenecks before they hit production and cause a fire drill with the business users?
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.