◆ Microsoft SQL Server

Monitor SQL Server 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 taskGenerate a report of all active connections to the 'Inventory' database on 'DBHOST05' that have…+
Generate a report of all active connections to the 'Inventory' database on 'DBHOST05' that have been idle for more than 30 minutes, including their login names and application names, by 3 PM today.
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 end-of-quarter reporting period next week, I need to identify any long-running…+
Before the end-of-quarter reporting period next week, I need to identify any long-running queries or blocking sessions that could impact report generation performance on the 'ReportingDB' database. Provide a detailed analysis of the top 10 most resource-intensive queries and any persistent blocking chains from the last 24 hours.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentUsers are reporting the 'Analytics' application is extremely slow, especially when generating…+
Users are reporting the 'Analytics' application is extremely slow, especially when generating daily sales reports.
Users are reporting the 'Analytics' application is extremely slow, especially when generating daily sales reports from the 'DataWarehouse' database. I'm seeing high CPU usage on the host, but no single query stands out as the culprit. I'm worried it's a cumulative effect of many inefficient queries or a deeper indexing issue that's hard to spot. The data analysts need these reports by 9 AM every day. What's the most likely diagnosis for this overall slowdown, and what's the best next step to quickly identify the performance bottleneck?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often discover performance bottlenecks only after users complain about slow applications,…+
I often discover performance bottlenecks only after users complain about slow applications.
I often discover performance bottlenecks only after users complain about slow applications, leading to urgent, reactive troubleshooting and user frustration. This means I'm always behind the curve. What habit should I change to proactively monitor and identify potential performance issues in our database systems before they impact the end-users?
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.