◆ Microsoft SQL Server

Use the Maintenance Plan Wizard

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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore I use the Maintenance Plan Wizard for the 'ProductionERP' database, make sure the plan…+
Before I use the Maintenance Plan Wizard for the 'ProductionERP' database, make sure the plan is optimized for our high-transaction environment. Configure it to only rebuild fragmented indexes above 30% and ensure the integrity check doesn't block critical operations.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentI used the Maintenance Plan Wizard for the 'ReportingDB' database, scheduling index rebuilds…+
I used the Maintenance Plan Wizard for the 'ReportingDB' database, but now users are complaining about slow queries every Sunday morning.
I used the Maintenance Plan Wizard for the 'ReportingDB' database, scheduling index rebuilds and statistics updates every Sunday morning. Now users are complaining about slow queries and timeouts during that window. I'm afraid I've made the performance worse. I can't tell if the tasks are running too long or conflicting with reporting jobs. What's the likely diagnosis, and what's the best next move to resolve the performance impact without sacrificing maintenance?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI frequently create maintenance plans using the wizard that cause performance issues or don't…+
I frequently create maintenance plans that cause performance issues or don't adequately address database health.
I frequently create maintenance plans using the wizard that cause performance issues or don't adequately address database health, forcing me to rework them later. My current approach is often a 'set it and forget it' mentality. What habit should I change to consistently create effective and performance-friendly maintenance plans that genuinely support database stability and speed?
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.