◆ Microsoft SQL Server

Implement SQL Server security best practices

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 taskGrant 'SELECT' permission on the 'Products' table in 'InventoryDB' to the 'MarketingTeam' login…+
Grant 'SELECT' permission on the 'Products' table in 'InventoryDB' to the 'MarketingTeam' login by 3 PM today.
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 grant this permission to the Marketing Team, make sure it aligns with our least…+
Before I grant this permission to the Marketing Team, make sure it aligns with our least privilege policy. Review their existing roles, identify any broader permissions they might already have, and flag any other databases or objects they might inadvertently gain access to.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentAuditing just flagged a user with 'sysadmin' rights who shouldn't have them, and I can't find…+
Auditing just flagged a user with 'sysadmin' rights who shouldn't have them.
Auditing just flagged a user with 'sysadmin' rights who shouldn't have them, and I can't find any documentation on why it was granted. I'm afraid to revoke it immediately in case it breaks a critical application, but I know it's a huge security risk. I don't know who approved it or what depends on it. What's the most likely diagnosis, and what's my best next move to secure the system 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 finding users with overly broad permissions or orphaned logins during audits, which…+
I keep finding users with overly broad permissions or orphaned logins during audits.
I keep finding users with overly broad permissions or orphaned logins during audits, which takes a lot of time to untangle and fix. I spend too much effort reactively cleaning up security issues. What habit should I change to ensure our security posture is consistently aligned with best practices and least privilege?
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.