◆ Microsoft SQL Server

Tune SQL Server performance

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 taskApply the missing index recommendation for the 'Customers' table on the 'OrderDate' column to…+
Apply the missing index recommendation for the 'Customers' table on the 'OrderDate' column to the 'SalesDB' database by end of day.
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 implement this index, make sure it's actually going to help. Show me the current query…+
Before I implement this index, make sure it's actually going to help. Show me the current query plans for the affected queries, estimate the performance gain, and flag any potential negative impact on write operations for the 'Customers' table.
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 nightly batch job for inventory updates is now running for 8 hours instead of 2, and…+
The nightly batch job for inventory updates is now running for 8 hours instead of 2.
The nightly batch job for inventory updates is now running for 8 hours instead of 2, and warehouse operations are getting delayed. I just saw a new statistics update job completed an hour before the batch started, but I don't know if that's the cause or if there's a new query plan. I'm afraid to roll back the statistics without understanding the full impact. What's the most likely diagnosis, and what's my best next move to get the batch job back on schedule?
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 constantly chasing down slow queries reported by users, often after hours, feeling like I'm…+
I'm constantly chasing down slow queries reported by users, often after hours.
I'm constantly chasing down slow queries reported by users, often after hours, feeling like I'm always reacting. I spend too much time manually analyzing individual query plans. What habit should I change to proactively identify and address performance bottlenecks before they become urgent user complaints?
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.