◆ Microsoft SQL Server

Monitor SQL Server performance and activity

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 the CPU utilization and active connections on the main production system, SQLPROD01,…+
Check the CPU utilization and active connections on the main production system, SQLPROD01, right now. I need to see if the recent spike is still happening before the morning rush starts.
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 report on the performance issues, show me the top 10 most resource-intensive queries…+
Before I report on the performance issues, show me the top 10 most resource-intensive queries from the last hour on the customer-facing database. I need to understand what's actually causing the slowdowns, not just that they're happening.
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 database just locked up again, right when the sales team needs their end-of-day reports. I…+
The database just locked up again during the critical end-of-day report run, and the sales team is furious they can't see their numbers.
The database just locked up again, right when the sales team needs their end-of-day reports. I saw a ton of blocked processes, but I can't tell if it's a single rogue query or something deeper with the new indexing. I'm afraid of blaming the wrong thing and having it happen again tomorrow. What's the most likely culprit, and what's the fastest way to get things moving for them without making it worse?
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 blindsided by performance issues that only show up during peak times, even after…+
I keep getting blindsided by performance issues that only show up during peak times, even after I think I've optimized.
I keep getting blindsided by performance issues that only show up during peak times, even after I think I've optimized. I spend too much time reacting instead of preventing. What habit should I change to anticipate these bottlenecks before they impact users, especially around month-end reporting?
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.