◆ Microsoft SQL Server

Manage database systems

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 taskCreate a new user 'Jenny.Smith' with read-only access to the 'CustomerData' database. Assign…+
Create a new user 'Jenny.Smith' with read-only access to the 'CustomerData' database. Assign her to the 'DataAnalysts' role. Ensure her password expires in 90 days and she is prompted to change it on first login.
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 provision this new 'CustomerData' database for the marketing team, make sure it's…+
Before I provision this new 'CustomerData' database for the marketing team, make sure it's optimized for their reporting needs. Create appropriate indexes on 'CustomerID', 'OrderDate', and 'Region' columns. Also, set up a daily job to refresh the 'MarketingSummary' materialized view overnight, so their dashboards are always current.
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 have to apply a critical security patch to the 'FinancialReporting' database tonight, but the…+
I need to apply a critical security patch, but the change window is tight, and I'm unsure about potential dependencies.
I have to apply a critical security patch to the 'FinancialReporting' database tonight, but the change window is only two hours, and I'm not entirely confident about all the downstream application dependencies. I'm afraid of breaking a critical report, but delaying the patch is a major security risk. What's the most likely hidden dependency I should worry about, and what's my best next move to quickly identify and mitigate potential issues before I start the patching process?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often spend too much time manually performing routine database maintenance like index…+
I frequently find myself manually performing routine maintenance tasks that should be automated.
I often spend too much time manually performing routine database maintenance like index rebuilds, backups, and integrity checks. This takes away from strategic work and introduces human error. What habit should I change in my database management approach to identify and implement automation for these repetitive tasks, so I can free up my time for more complex problem-solving and improve overall database reliability?
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.