◆ Microsoft Azure

Rename SQL Azure 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 taskRename the SQL database currently named 'old-crm-db-prod' to 'customer-relations-prod-2024'.…+
Rename the SQL database currently named 'old-crm-db-prod' to 'customer-relations-prod-2024'. Confirm the rename is successful and connections are restored.
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 the end of the month, rename the 'old-crm-db-prod' database to reflect its current…+
Before the end of the month, rename the 'old-crm-db-prod' database to reflect its current purpose and year. The new name needs to be clear and consistent with our other production databases. Ensure minimal downtime and verify all dependent applications can still connect and function correctly after the change.
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 rename a critical production SQL database, 'legacy-reporting-db', as part of our…+
I need to rename a critical production SQL database, but I'm worried about breaking dependencies.
I need to rename a critical production SQL database, 'legacy-reporting-db', as part of our migration project. I'm worried about breaking existing applications and reports that rely on its current name, especially the finance team's month-end reports. I can't tell if all connection strings are documented or if there are hardcoded references I'm missing. What's the safest way to rename this database with minimal downtime and ensure all dependencies are updated without causing a major outage for the finance team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe frequently have databases with inconsistent or outdated naming conventions, making it…+
We frequently have databases with inconsistent or outdated naming conventions.
We frequently have databases with inconsistent or outdated naming conventions, making it difficult to identify their purpose or environment quickly. This leads to confusion and potential errors during maintenance or incident response. What habit should I change in our database provisioning or review process to enforce clear, consistent naming conventions from the start, avoiding these issues down the line?
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.