◆ Microsoft SQL Server

Drop database when in use

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 taskDrop the 'Staging_Data_2023' database, even if there are active connections, so we can refresh…+
Drop the 'Staging_Data_2023' database, even if there are active connections, so we can refresh it for the new quarter's load.
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 drop 'Staging_Data_2023', ensure it's safe to proceed. Check for any long-running…+
Before I drop 'Staging_Data_2023', ensure it's safe to proceed. Check for any long-running queries or critical processes that might be using it, and tell me if dropping it will impact any active reports or user sessions. I need to avoid disrupting the sales team's morning dashboards.
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 tried to drop the 'Old_Archive_2022' database, but it failed saying it's in use. I checked…+
I tried to drop the 'Old_Archive_2022' database, but it failed with an error about active connections, even though I see no users logged in.
I tried to drop the 'Old_Archive_2022' database, but it failed saying it's in use. I checked active sessions and there's nothing obvious. The finance team needs this space freed up by end of day Friday. I'm afraid I'll force it and crash something critical. What's likely holding it open, and what's the safest way to drop it without causing a ripple effect?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep struggling to drop old development or staging databases because of lingering connections…+
I keep struggling to drop old development or staging databases because of lingering connections.
I keep struggling to drop old development or staging databases because of lingering connections I can't easily identify. It wastes a lot of time and sometimes I have to wait for off-hours. What habit should I change to make sure these databases can be dropped cleanly and quickly when they are no longer needed, without having to hunt down phantom connections every time?
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.