◆ Microsoft SQL Server

Troubleshoot SQL Maintenance Cleanup task

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 taskI need to fix the database Maintenance Cleanup task on the production system. It's failing…+
I need to fix the database Maintenance Cleanup task on the production system. It's failing every night at 2 AM, and the transaction logs are filling up disk space. Get it running successfully by tomorrow morning.
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 acceptThe database Maintenance Cleanup task keeps failing on the production system, and I'm getting…+
The database Maintenance Cleanup task keeps failing on the production system, and I'm getting alerts about disk space. Before I restart it, check the error logs for common issues and suggest a more robust way to handle log file cleanup going forward, so this doesn't keep happening.
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 database Maintenance Cleanup task on the production system just failed for the third night…+
The SQL Maintenance Cleanup task failed again, and the disk is almost full.
The database Maintenance Cleanup task on the production system just failed for the third night in a row, and now the C drive is at 98%. My manager, Susan, is already asking about system performance. I'm afraid of a full outage before morning, but I also can't just delete files without understanding the impact. What's the fastest way to diagnose why it's failing and safely free up enough space to get us through the night without breaking anything?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend too much time reacting to critical disk space alerts from failed database Maintenance…+
I keep getting pulled into urgent disk space issues from failed maintenance tasks.
I spend too much time reacting to critical disk space alerts from failed database Maintenance Cleanup tasks. It's usually transaction logs or old backups. I need a better habit for proactive monitoring and automated remediation, so I'm not always fighting fires and can focus on development work instead.
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.