◆ Microsoft SQL Server

Manage SQL Server permissions and access

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 read-only access to the 'SalesData' database for the new BI analyst, Sarah Chen, by…+
Grant read-only access to the 'SalesData' database for the new BI analyst, Sarah Chen, by Friday. Make sure she can only see the 'Orders' and 'Customers' tables, and nothing else.
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 Sarah Chen access to SalesData, make sure she can't accidentally lock up any…+
Before I give Sarah Chen access to SalesData, make sure she can't accidentally lock up any tables. Set up her permissions so she can query without any risk of contention or blocking for other users.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSarah Chen says she can't see the 'Orders' table, but my script ran without errors, and the…+
The new BI analyst just reported she can't see the data she needs, but the logs show I granted her access.
Sarah Chen says she can't see the 'Orders' table, but my script ran without errors, and the permissions look right. The sales team needs her reports by end of day. I'm afraid I missed a dependency or an inherited permission. What's the most likely reason she's still blocked and what should I check first?
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 getting calls from users who can't access data even after I grant them permissions. It's…+
Users keep getting blocked from data they need, even after I grant access.
I keep getting calls from users who can't access data even after I grant them permissions. It's always a scramble to figure out why. I'm losing too much time and credibility trying to diagnose these. What habit should I change to make sure new access grants work correctly the first time?
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.