◆ Microsoft SQL Server

Query SQL Server for 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
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 taskList all users and their explicit permissions on the 'HRData' database, specifically for the…+
List all users and their explicit permissions on the 'HRData' database, specifically for the 'EmployeeDetails' table. Include any inherited permissions from roles.
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 the new 'SalesAnalyst' role access to the 'SalesFigures' database, provide a…+
Before I grant the new 'SalesAnalyst' role access to the 'SalesFigures' database, provide a summary of all existing permissions for similar analyst roles. Highlight any potential over-privileging or security gaps if I just replicate the 'MarketingAnalyst' permissions.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur finance manager, Sarah, says she can't access the 'QuarterlyRevenue' view in the 'Finance'…+
A user claims they can't access a specific view in the 'Finance' database, but I see they are part of the correct role.
Our finance manager, Sarah, says she can't access the 'QuarterlyRevenue' view in the 'Finance' database, even though she's a member of the 'FinanceUsers' role which has SELECT permissions. I've double-checked her role membership. What common permission gotcha am I likely missing here, and how should I quickly diagnose why she's being denied access?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI find myself scrambling to gather permission details whenever a security audit or compliance…+
Permission audits are always a scramble when a security incident or compliance request comes up.
I find myself scrambling to gather permission details whenever a security audit or compliance request comes in, often discovering inconsistencies. This reactive approach is inefficient. What habit should I change to maintain a clearer, more auditable understanding of permissions across all critical databases on an ongoing basis?
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.