◆ Microsoft Azure

Drop all tables and reset Azure SQL Database

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 taskConnect to the 'DevTestDB' SQL Database and drop all tables. Then, reset it to its initial…+
Connect to the 'DevTestDB' SQL Database and drop all tables. Then, reset it to its initial schema. The dev team needs a clean slate for their testing 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 acceptBefore I drop all tables and reset the 'StagingDB' SQL Database, confirm that there are no…+
Before I drop all tables and reset the 'StagingDB' SQL Database, confirm that there are no active connections or critical processes using it. Give me a quick checklist to ensure I don't interrupt any ongoing work for the QA team or accidentally lose any data that might still be needed.
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 need to drop all tables and reset the 'UATDatabase' for a new round of user acceptance…+
I need to reset a database but I'm unsure if anyone is currently using it.
I need to drop all tables and reset the 'UATDatabase' for a new round of user acceptance testing, but I'm not sure if any users are still active on it. I'm afraid of wiping out someone's work or interrupting a critical test. What's the best way to quickly check for active sessions and gracefully disconnect them before I proceed, ensuring I don't cause an incident for the UAT team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI find that resetting SQL Databases for testing or development environments often leads to…+
Resetting databases often leads to unexpected data loss or downtime.
I find that resetting SQL Databases for testing or development environments often leads to unexpected data loss or downtime because I miss a dependency or an active user. This costs me credibility with the dev and QA teams. What habit should I change to systematically ensure all necessary checks are performed and stakeholders are informed before I initiate a database reset?
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 Azure'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.