◆ Microsoft SQL Server

Track progress of CREATE INDEX command

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 taskTrack the progress of the `CREATE INDEX IX_OrderDate` command currently running on the…+
Track the progress of the `CREATE INDEX IX_OrderDate` command currently running on the `Sales.Orders` table. I need to know when it's done so I can inform the BI team it's safe to run their reports.
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 kick off this large index creation on `Sales.Transactions`, I need to know its…+
Before I kick off this large index creation on `Sales.Transactions`, I need to know its estimated completion time and if it's going to cause significant blocking for the users. Give me the current progress and any potential impact on active queries.
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 `CREATE INDEX IX_CustomerID` command on the `Customers.Orders` table has been running for…+
A critical `CREATE INDEX` command has been running for hours, and I have no idea if it's stuck or just slow.
The `CREATE INDEX IX_CustomerID` command on the `Customers.Orders` table has been running for over three hours, much longer than expected. I'm afraid it might be deadlocked or making no progress, but I can't tell without disrupting it. How do I safely check its actual progress and determine if it's genuinely working or if I need to intervene without causing a rollback?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently underestimate the time and resource impact of large index creations, leading to…+
I frequently underestimate the time and resource impact of large index operations, leading to user complaints and missed maintenance windows.
I frequently underestimate the time and resource impact of large index creations, leading to user complaints about slow queries and missed maintenance windows. This impacts my credibility with the operations team. What habit should I change to better predict the duration and resource consumption of these operations, allowing me to schedule them more effectively and communicate realistic timelines?
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.