◆ Microsoft SQL Server

Automate database tasks for 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 'SalesDataProd' database to automatically back up daily at 2 AM PST, retaining…+
Set up the 'SalesDataProd' database to automatically back up daily at 2 AM PST, retaining backups for 30 days. Confirm the backup succeeded for yesterday 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 hand off the new 'CustomerPortalDB' to the development team, configure its automated…+
Before I hand off the new 'CustomerPortalDB' to the development team, configure its automated backups to be resilient. I need to know if the primary region fails, the backups are still accessible and can restore quickly, minimizing data loss for our users.
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 nightly backup for 'InventoryDB' failed again last night, showing a 'disk full'…+
The automated nightly backup for 'InventoryDB' failed again, for the third time this week, and the on-call engineer is asking why and when it will be fixed.
The automated nightly backup for 'InventoryDB' failed again last night, showing a 'disk full' error, but I checked and there's plenty of space. We had a large data import yesterday afternoon. I'm worried this is a symptom of something bigger, and I can't tell the on-call engineer we're still investigating. What's the most likely cause, and what's the fastest way to get a successful backup tonight?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent calls about failed automated tasks and unexpected resource…+
I keep getting pulled into urgent calls about failed automated tasks and unexpected resource spikes.
I keep getting pulled into urgent calls about failed automated tasks and unexpected resource spikes in our databases. It feels like I'm always reacting. What habit should I change to anticipate these issues, especially around scaling and resource limits, before they impact our users or trigger alerts?
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.