◆ Microsoft SQL Server

Shrink all files for all databases

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
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskShrink all data and log files for every database on this system. The C drive is critically low…+
Shrink all data and log files for every database on this system. The C drive is critically low on space, and I need to free up as much as possible before the end of the day.
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 shrinking all database files, identify the top 5 databases with the most reclaimable…+
Before shrinking all database files, identify the top 5 databases with the most reclaimable space and only shrink those. I need to target the biggest wins for disk space without causing unnecessary fragmentation on less critical databases, especially before the weekend.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just kicked off a shrink operation for all database files because disk space is critically…+
I tried to shrink all database files, but the process is taking forever, and I'm worried about blocking production users.
I just kicked off a shrink operation for all database files because disk space is critically low, but it's running incredibly slowly, and I'm afraid it's going to block our production applications during peak hours. Our operations lead is already on my case about recent performance issues. What's the most likely reason for this slowness, and what's the best next move to either speed it up or safely stop it without causing more disruption, so I can free up space without impacting users?
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 find myself in a reactive cycle of shrinking all database files when disk space gets…+
I frequently resort to aggressive database shrinking for disk space, leading to performance issues and re-growing files.
I often find myself in a reactive cycle of shrinking all database files when disk space gets critical, which then leads to performance problems from fragmentation and files just growing back. This creates a constant struggle to manage storage efficiently. What habit should I change to proactively manage database file growth and disk space, so I can avoid these reactive shrinks and maintain consistent database performance?
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.