◆ Microsoft SQL Server

Manage SQL Server roles and permissions

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 taskGrant 'SalesTeam_Reader' role to the login 'User_Priya' on the 'SalesData'…+
Grant 'SalesTeam_Reader' role to the login 'User_Priya' on the 'SalesData' database.
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 give the new marketing analyst, David, access to the 'CustomerEngagement' database, I…+
Before I give the new marketing analyst, David, access to the 'CustomerEngagement' database, I need to make sure he can only see what's relevant to his job and nothing sensitive. The finance director is very strict about data privacy. What's the most secure and least cumbersome way to set up his permissions so he can do his work without over-privileging him?
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 intern, Sarah, can't access the 'ReportingDB' even though I added her to the…+
The new intern, Sarah, can't access the 'ReportingDB' even though I added her to the 'ReportUsers' group.
The new intern, Sarah, can't access the 'ReportingDB' even though I added her to the 'ReportUsers' group, which has read access to all relevant tables. She's getting a 'permission denied' error when trying to run a simple SELECT query. Her manager, Mark, needs her to pull data for a presentation by end of day. I'm afraid I've missed a nested permission or an implicit deny. What's the most likely reason for her access issue, and how can I quickly verify and fix it without granting excessive permissions?
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 get requests from users who can't access data they need, or worse, have too much…+
I frequently get requests from users who can't access data they need, or worse, have too much access.
I frequently get requests from users who can't access data they need, or worse, have too much access, leading to security concerns from the audit team. Managing roles and permissions feels like a constant firefighting exercise, and I'm losing time and credibility. What habit should I change to proactively manage database roles and permissions, ensuring users have just the right access from day one?
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.