◆ Microsoft SQL Server

Troubleshoot high CPU usage 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 taskCheck the SQL Server instance 'PROD_CRM' for any processes currently consuming high CPU. I need…+
Check the SQL Server instance 'PROD_CRM' for any processes currently consuming high CPU. I need to identify the top 3 culprits and their associated queries so I can report back to the CRM team by lunch.
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 the finance team's month-end close, investigate the 'PROD_FINANCE' SQL Server instance…+
Before the finance team's month-end close, investigate the 'PROD_FINANCE' SQL Server instance for recurring high CPU usage patterns. Look for inefficient queries, missing statistics, or poorly optimized stored procedures that consistently spike CPU, especially during their critical reporting window. Highlight what could be optimized to ensure a smooth close.
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 'ReportingDB' database instance's CPU is pegged at 95%, and the marketing team is furious…+
CPU on the 'ReportingDB' server just spiked to 95%, and the marketing team can't run their campaign reports.
The 'ReportingDB' database instance's CPU is pegged at 95%, and the marketing team is furious because their campaign reports are failing. I see a few queries running, but none look exceptionally bad, and I can't tell which one is actually causing the spike. What's the fastest way to identify the exact queries or processes responsible for this extreme CPU usage, and how can I bring it down immediately without crashing the database instance?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm frequently surprised by sudden high CPU usage on our production database servers, leading…+
High CPU alerts often hit me by surprise, disrupting critical operations.
I'm frequently surprised by sudden high CPU usage on our production database servers, leading to downtime and frustrated users. I need to shift from reactive firefighting to proactive management. What daily or weekly habits should I implement to monitor and optimize CPU usage, predicting and preventing these spikes before they become emergencies?
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.