◆ Microsoft Azure

Automate database maintenance on 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 a weekly maintenance job for the customer database, running every Sunday at 2 AM UTC, to…+
Set up a weekly maintenance job for the customer database, running every Sunday at 2 AM UTC, to rebuild indexes and update statistics. Make sure it logs all operations and sends an alert to the database team if it fails.
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 this database maintenance automation for the customer database, ensure it…+
Before I finalize this database maintenance automation for the customer database, ensure it scales efficiently. Can we use a more granular index rebuild strategy for frequently accessed tables and only update statistics on modified tables to minimize performance impact during the window?
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 database maintenance job failed again last night, and the application performance…+
The automated database maintenance job in Azure SQL failed again last night, right after a major application update, and the logs aren't clear.
The automated database maintenance job failed again last night, and the application performance is suffering. The logs show a generic timeout, but I can't tell if it's a resource issue, a lock contention from the recent application update, or something else. I'm worried about data integrity and the impact on our users. What's the most likely cause, and what's the first thing I should check to diagnose this?
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 losing time diagnosing intermittent failures in our SQL maintenance jobs, especially…+
I keep losing time diagnosing intermittent failures in our Azure SQL maintenance jobs, especially after application deployments.
I keep losing time diagnosing intermittent failures in our SQL maintenance jobs, especially after application deployments. The current setup doesn't give me enough context to quickly pinpoint root causes. What habit should I change in how I design or monitor these jobs to anticipate and prevent these post-deployment issues, instead of reacting to them?
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 Azure'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.