◆ Microsoft SQL Server

Configure database-level roles in SQL Server

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 taskCreate a new database-level role named 'App_Readers' for the 'MarketingDB' database. Grant this…+
Create a new database-level role named 'App_Readers' for the 'MarketingDB' database. Grant this role SELECT permissions on all tables within the 'Campaigns' schema. Assign the existing login 'MarketingAppUser' to this new role by end of day.
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 finalize the security for the new 'Inventory' database, make sure the database-level…+
Before I finalize the security for the new 'Inventory' database, make sure the database-level roles are robust. Define a 'Inventory_Admins' role with full control over the database, a 'Inventory_Editors' role with read/write access to all tables, and a 'Inventory_Viewers' role with read-only access, ensuring no one can accidentally drop tables.
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 finance team is complaining that their reports on 'FinancialData' are running slowly, and…+
The finance team needs to run complex reports on the 'FinancialData' database, but their existing 'db_datareader' role is causing performance issues due to missing index rebuild permissions.
The finance team is complaining that their reports on 'FinancialData' are running slowly, and I've diagnosed it as a need for them to rebuild specific indexes after large data loads. Their 'db_datareader' role doesn't allow this, and I'm hesitant to give them 'db_owner' or 'db_ddladmin' due to the risk. What's the most granular database-level role or permission I can grant them to only rebuild indexes on specific tables without giving them broader DDL rights, and how do I ensure this doesn't open up other vulnerabilities?
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 losing time and increasing security risk by granting individual object permissions to…+
I frequently find myself granting individual object permissions to users because the standard database roles don't quite fit, leading to a tangled mess.
I keep losing time and increasing security risk by granting individual object permissions to users because the standard database roles don't quite fit their needs, leading to a tangled mess of permissions that's impossible to audit. What habit can I change to ensure I consistently use well-defined, purpose-built database-level roles that minimize individual object grants, making our security posture clearer and more manageable?
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.