◆ Microsoft SQL Server

Clear caches for performance comparison

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 taskClear the data cache and the procedure cache for the 'ReportingDB' database on the system…+
Clear the data cache and the procedure cache for the 'ReportingDB' database on the system 'SQL_PROD_01' so I can get accurate performance numbers for the new query.
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 run the final performance comparison for the 'Inventory_Lookup' stored procedure,…+
Before I run the final performance comparison for the 'Inventory_Lookup' stored procedure, clear all relevant caches on the 'WarehouseDB' database system. Also, ensure the test environment is isolated from any other active queries, so my benchmark numbers are reliable for the team meeting tomorrow.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to compare the performance of the 'Generate_Monthly_Report' procedure before and…+
My 'before' and 'after' performance tests for the new stored procedure are showing inconsistent results, and I can't explain why.
I'm trying to compare the performance of the 'Generate_Monthly_Report' procedure before and after my optimization, but the numbers are all over the place, even after clearing caches. I'm worried I'm missing some hidden caching mechanism or background activity. What's the most common reason for this inconsistency, and what's the best way to ensure a truly 'clean slate' for my next test run?
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 waste a lot of time trying to get consistent performance benchmarks for new queries or…+
I frequently struggle to get consistent, reliable performance benchmarks because I'm not confident I'm clearing all relevant caches or isolating tests properly.
I often waste a lot of time trying to get consistent performance benchmarks for new queries or stored procedures. I suspect I'm not always clearing all the right caches or isolating my tests effectively. What habit should I change to ensure I consistently achieve reliable and repeatable performance test results every time?
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.