◆ Microsoft SQL Server

Create SQL Server maintenance plan

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 taskCreate a maintenance plan to rebuild all indexes on the 'Sales' database every Sunday at 3 AM,…+
Create a maintenance plan to rebuild all indexes on the 'Sales' database every Sunday at 3 AM, and then update statistics with full scan on the same database.
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 put this new maintenance plan into production, I need to ensure it won't cause any…+
Before I put this new maintenance plan into production, I need to ensure it won't cause any performance degradation or locking issues during our peak online shopping hours on Saturday night. The plan includes index rebuilds and statistics updates. Can we identify the most fragmented indexes and outdated statistics and prioritize those, rather than a full rebuild, to minimize impact and ensure the website remains responsive?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are complaining that the 'Customer_Order_History' report is taking forever to load,…+
Users are complaining about slow report performance, and I suspect a fragmented index.
Users are complaining that the 'Customer_Order_History' report is taking forever to load, especially on Friday afternoons. I suspect index fragmentation on the 'Orders' table, but I'm hesitant to just run a full index rebuild during business hours, given the impact it could have. I don't know which specific indexes are most affected or if an online rebuild is even feasible. What's the safest and most effective way to diagnose the actual problem and fix it without disrupting our critical end-of-week processes?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly reacting to user complaints about slow queries and report performance, often…+
I keep reacting to performance complaints that could have been prevented by better maintenance.
I'm constantly reacting to user complaints about slow queries and report performance, often finding that the root cause is outdated statistics or fragmented indexes. It feels like I'm always playing catch-up. What habit should I change to proactively monitor database health and implement maintenance plans that prevent these performance issues from impacting users in the first place, rather than just fixing them after they've become a problem?
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.