◆ Microsoft Azure

Stop SQL Azure DB when not 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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskShut down the SQL database named 'dev-analytics-db-1' in the 'dev-rg-analytics' resource group…+
Shut down the SQL database named 'dev-analytics-db-1' in the 'dev-rg-analytics' resource group by Friday at 5 PM PST. Make sure to confirm it's not actively being used for testing before you do.
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 shut down the 'dev-analytics-db-1' database for the weekend, show me a quick overview…+
Before I shut down the 'dev-analytics-db-1' database for the weekend, show me a quick overview of its recent activity and any active connections in the last 24 hours. I need to be sure no one's work gets interrupted, especially the new intern's project.
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 tried to shut down 'dev-analytics-db-1' for the weekend, but it's still showing active…+
I tried to shut down the dev database, but it's showing active connections from a service principal I don't recognize.
I just tried to shut down 'dev-analytics-db-1' for the weekend, but it's still showing active connections from a service principal I don't recognize. The testing team said they were done, and I'm worried about breaking something if I force it. What's the likely source of these connections, and what's the safest way to proceed without causing an outage?
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 forgetting to shut down our development databases at the end of the day or over…+
I consistently forget to shut down our dev databases after hours, leading to unnecessary costs.
I keep forgetting to shut down our development databases at the end of the day or over weekends, and we're racking up unnecessary costs. It's a small thing, but it adds up. What's a better habit or system I can put in place to ensure these databases are paused when not in active use, without relying on my memory?
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.