◆ Microsoft Azure

View roles and permissions for database user

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 taskShow me all roles and permissions assigned to the user 'SQL_Analytics_User' on the…+
Show me all roles and permissions assigned to the user 'SQL_Analytics_User' on the 'ProductionDB' 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 we grant 'SQL_Analytics_User' access to the new 'MarketingData' database, provide a…+
Before we grant 'SQL_Analytics_User' access to the new 'MarketingData' database, provide a comprehensive list of all their current roles and permissions across all SQL databases. Highlight any elevated permissions that might pose a security risk if duplicated in the new database, so we can apply the principle of least privilege.
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 data analyst, Maria, can't access a specific table in the 'ReportingDB' database, but when…+
A user is complaining they can't access a table, but their permissions look correct to me.
Our data analyst, Maria, can't access a specific table in the 'ReportingDB' database, but when I check her 'Reporting_Reader' role, it seems to have all the necessary permissions. The security audit is next week, and I'm worried about inconsistencies. I can't tell her I'm unsure. What's the most thorough way to diagnose why 'SQL_Analytics_User' (Maria's account) cannot access that table, and what specific steps should I take to verify effective 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 spend too much time trying to figure out the effective permissions for database…+
I constantly struggle to understand the effective permissions for database users, especially with complex role assignments.
I frequently spend too much time trying to figure out the effective permissions for database users, especially when roles are nested or inherited. This leads to access issues and security concerns. What habit should I change to more efficiently and accurately assess a user's actual permissions on a SQL database, so I can confidently grant and revoke access without unintended consequences?
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 Azure'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.