◆ Microsoft Azure

Perform database maintenance tasks

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 taskRun the weekly database consistency check on the production customer database. Make sure it…+
Run the weekly database consistency check on the production customer database. Make sure it completes before 6 AM UTC 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 run the weekly consistency check on the customer database, confirm the resource group…+
Before I run the weekly consistency check on the customer database, confirm the resource group has enough available capacity to handle the load spike, and flag any potential conflicts with other scheduled jobs.
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 weekly consistency check just failed on the customer database, again. It's Friday morning,…+
The database consistency check just failed for the third time this month on the customer database.
The weekly consistency check just failed on the customer database, again. It's Friday morning, and the report is due to the VP by noon. I'm afraid to rerun it without understanding why it's failing, but I can't find clear errors in the logs. What's the most likely cause for repeated consistency check failures, and what's the safest next step to get this reported by noon?
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 database performance issues after maintenance…+
I keep losing time diagnosing intermittent database performance issues after maintenance.
I keep losing time diagnosing intermittent database performance issues after maintenance windows. We often rush through post-maintenance checks. What habit should I change to ensure we catch these problems before they impact users, instead of reacting to tickets later?
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.