◆ Microsoft SQL Server

Configure server-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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskAdd the Windows group 'AD\DB_Admins' to the 'sysadmin' role on the 'PROD_SQL_SERVER_01'…+
Add the Windows group 'AD\DB_Admins' to the 'sysadmin' role on the 'PROD_SQL_SERVER_01' instance. Verify the change immediately and notify the IT security lead.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentOur new monitoring tool's service account, 'MonitorSVC_PROD', needs to collect performance…+
A new monitoring tool needs to collect performance metrics from the SQL Server instance, but its service account doesn't have the necessary server-level permissions.
Our new monitoring tool's service account, 'MonitorSVC_PROD', needs to collect performance metrics from the SQL Server instance, but it's currently failing due to insufficient server-level permissions. I'm afraid of giving it 'sysadmin' or 'public' access, which is too broad and risky. What's the most precise server-level role or set of permissions I can grant this service account to only read performance counters and server state without granting any administrative or data access, and how do I confirm it's truly locked down?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI'm constantly losing credibility and risking security breaches because I keep finding myself…+
I keep finding myself granting 'sysadmin' or 'public' to new tools or users for convenience, only to regret it later during security audits.
I'm constantly losing credibility and risking security breaches because I keep finding myself granting 'sysadmin' or 'public' system-level roles to new tools or users for convenience, only to regret it later during security audits. It's a quick fix that creates long-term problems. What habit can I change to ensure I always assign the absolute minimum necessary system-level permissions, forcing me to think critically about each request instead of defaulting to broad access?
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.