◆ Microsoft SQL Server

Create and manage SQL Server maintenance plans

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 daily backup plan for the 'Finance' database, retaining backups for 7 days, and…+
Set up a daily backup plan for the 'Finance' database, retaining backups for 7 days, and schedule it to run every night at 2 AM. Ensure the backup files are compressed and stored on the shared network drive.
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 maintenance plan for the 'Reporting' database, identify any fragmentation…+
Before I finalize the maintenance plan for the 'Reporting' database, identify any fragmentation issues on its largest tables and suggest an optimal reindex schedule. Also, check the transaction log size and recommend a suitable log backup frequency to prevent it from growing too large.
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 index rebuild job for the 'Archive' database has failed for the past three Sundays.…+
The weekly index rebuild job for the 'Archive' database is failing every Sunday night.
The weekly index rebuild job for the 'Archive' database has failed for the past three Sundays. The error logs are vague, mentioning 'resource contention,' but I can't pinpoint the exact cause. Other jobs run fine. What's the most likely source of this contention, and what's the first thing I should check to get it running successfully again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often set up maintenance plans and then don't revisit them until a performance issue or a…+
Maintenance plans often get created and then forgotten until a problem arises.
I often set up maintenance plans and then don't revisit them until a performance issue or a full disk alarm goes off. This leads to reactive firefighting. What habit should I change to proactively review and optimize maintenance plans, ensuring they remain effective as database usage evolves?
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.