◆ Microsoft Azure

Re-create database for Entity Framework

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 taskRecreate the database for the Entity Framework application using the existing schema, ensuring…+
Recreate the database for the Entity Framework application using the existing schema, ensuring all connection strings are updated for the dev environment and that it's ready for testing by end of day Friday.
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 recreating the database for the Entity Framework application, make sure the new…+
Before recreating the database for the Entity Framework application, make sure the new configuration can handle the expected load from the sales team's reporting module. Flag any potential bottlenecks or missing indexes that might slow down their queries.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe database recreation for the Entity Framework application failed for the third time, and the…+
The database recreation for Entity Framework failed again, and now the dev environment is down.
The database recreation for the Entity Framework application failed for the third time, and the dev environment is completely offline. The last error message was about a permissions issue, but I'm logged in as admin. Priya from QA is blocked, and the sales demo is tomorrow. I can't tell my manager it's down again. What's the most likely cause for this intermittent failure, and what's the safest way to get it back up without losing more time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly losing hours trying to get our Entity Framework dev databases consistently…+
I keep losing hours trying to get dev databases consistently recreated for our Entity Framework apps.
I'm constantly losing hours trying to get our Entity Framework dev databases consistently recreated and connected. It feels like every time there's a new hiccup. What habit should I change to make this process more reliable and less of a time sink, so I'm not scrambling before every release?
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.