◆ Microsoft SQL Server

Secure SQL managed instances

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
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskApply the latest security patch, KB5027225, to the HR and Payroll database managed instances.…+
Apply the latest security patch, KB5027225, to the HR and Payroll database managed instances. Verify successful application and restart services if required, aiming for completion by end of day Tuesday.
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 external audit next month, review the user permissions for all critical production…+
Before the external audit next month, review the user permissions for all critical production databases, especially those handling sensitive customer data. Identify any accounts with excessive privileges or inactive users that still have access, and suggest specific actions to tighten security without disrupting legitimate operations.
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 new marketing intern accidentally got 'sysadmin' rights to the customer segmentation…+
The new marketing intern accidentally got 'sysadmin' rights to the customer segmentation database, and I just found out.
The new marketing intern accidentally got 'sysadmin' rights to the customer segmentation database, and I just found out. I'm terrified of a data breach or accidental deletion, but I don't want to cause a panic by revoking it immediately without understanding the full impact. What's the fastest, least disruptive way to assess what they might have accessed or changed, and then safely revert their permissions without drawing undue attention?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find myself reacting to security vulnerabilities or accidental over-privileging of…+
I frequently find myself reacting to security vulnerabilities or accidental over-privileging of user accounts.
I frequently find myself reacting to security vulnerabilities or accidental over-privileging of user accounts, especially when new team members join or roles change. This 'clean-up' takes time and carries risk. What habit should I change to proactively manage user access and permissions, ensuring least privilege is consistently applied from the start, rather than fixing mistakes after they happen?
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.