◆ Microsoft SQL Server

Check if a user exists in a database

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 taskCheck if 'john.doe' exists as a user in the 'HR_PayrollDB'…+
Check if 'john.doe' exists as a user in the 'HR_PayrollDB' 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 I tell Sarah from HR that John Doe has access, check if 'john.doe' exists as a user in…+
Before I tell Sarah from HR that John Doe has access, check if 'john.doe' exists as a user in the 'HR_PayrollDB' database and what roles or permissions he currently has. I need to make sure he has the correct access level for the new payroll system by end of day.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMaria from Finance says she can't access the 'Financial_AuditDB', but when I checked,…+
A user claims they can't access a specific database, but my initial checks show they exist, creating confusion.
Maria from Finance says she can't access the 'Financial_AuditDB', but when I checked, 'maria.rodriguez' is listed as a user. I'm afraid she might have an old login or permissions issue that's not immediately obvious. What's the most common reason a user exists but still can't access a database, and what's the best next step to diagnose her actual access problem before she misses the deadline?
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 pulled into user access issues, spending too much time manually checking if a…+
I spend too much time manually verifying user access when people report issues, often finding the same common misconfigurations.
I keep getting pulled into user access issues, spending too much time manually checking if a user exists and what their permissions are. This feels inefficient. What habit should I change to more quickly and accurately diagnose user access problems, so I can address them faster and reduce interruptions?
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.