◆ Microsoft SQL Server

Manage SQL Server Agent jobs with Availability Groups

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 taskFor the 'Nightly_Backup' job, ensure it fails over correctly to the secondary replica…+
For the 'Nightly_Backup' job, ensure it fails over correctly to the secondary replica 'SQLAG-Node2' if 'SQLAG-Node1' is down. Update the job step to run the backup on the active replica only, and send a success notification to the 'DBA_Alerts' distribution list by Friday.
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 hand off the 'Data_Refresh' job to the new analyst, make sure it's resilient across…+
Before I hand off the 'Data_Refresh' job to the new analyst, make sure it's resilient across our availability groups. Set it up so it always runs on the primary, handles failovers gracefully, and logs any connection issues clearly so they don't have to guess what went wrong.
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 'Daily_ETL' job failed again this morning after the 'ProdAG' availability group failed over…+
The 'Daily_ETL' job failed again after the recent failover of the 'ProdAG' availability group.
The 'Daily_ETL' job failed again this morning after the 'ProdAG' availability group failed over to 'SQLAG-Node3'. The error message is vague, 'Cannot connect to database'. The business is expecting the updated reports by 9 AM. I'm afraid this will cause data staleness and a call from the finance team. I can't tell if the job itself is misconfigured for AGs or if there's a listener issue. What's the likely diagnosis and the best next move to get this job running on the new primary?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time our availability groups fail over, several critical scheduled jobs break, requiring…+
Availability Group failovers consistently break scheduled jobs, costing hours of manual intervention.
Every time our availability groups fail over, several critical scheduled jobs break, requiring manual fixes and delaying data availability. I'm constantly losing time troubleshooting these post-failover issues and credibility with the business. What habit should I change in how I configure and manage these jobs to prevent this recurring disruption?
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.