◆ Microsoft SQL Server

Automate management tasks in Azure SQL

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 the automated weekly backup of the Azure database 'CustomerDataProd' to blob storage,…+
Set up the automated weekly backup of the Azure database 'CustomerDataProd' to blob storage, ensuring it runs every Sunday at 2 AM UTC and retains the last four backups. Confirm the backup completes successfully.
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 finalize the Azure database 'CustomerDataProd' automation, make sure the backup…+
Before I finalize the Azure database 'CustomerDataProd' automation, make sure the backup schedule is resilient. Add a retry logic for failed backups and set up email notifications to the 'dba@example.com' distribution list if a backup fails or takes longer than 3 hours. Also, confirm the storage account has the right permissions.
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 weekly backup for 'CustomerDataProd' failed again last night, and the one before…+
The automated weekly backup for 'CustomerDataProd' failed for the second time in a row, and I can't see an obvious network issue or credential problem.
The automated weekly backup for 'CustomerDataProd' failed again last night, and the one before that. I've checked network connectivity and the service principal credentials, but everything looks fine. The logs just show a generic 'backup failed' message. I'm worried about data loss and the upcoming audit. What's the most likely root cause for a persistent backup failure that isn't network or credential related, and what's the quickest way to diagnose it without impacting production performance?
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 losing too much time each week manually verifying Azure database backup completion and…+
I keep spending too much time manually checking Azure SQL database backup statuses and troubleshooting failures.
I'm losing too much time each week manually verifying Azure database backup completion and troubleshooting the occasional failures. This takes away from proactive performance tuning. What habit should I change to ensure I have reliable, hands-off visibility into backup success and failure across all our critical databases without having to log in and check each one individually every Monday morning?
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.