◆ Microsoft SQL Server

Recover deleted records

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 taskI need to recover the records that were accidentally deleted from the `Marketing.Campaigns`…+
I need to recover the records that were accidentally deleted from the `Marketing.Campaigns` table yesterday around 2 PM. Restore them to their state just before the deletion occurred.
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 attempt to recover these deleted `Inventory.Products` records, I need to understand…+
Before I attempt to recover these deleted `Inventory.Products` records, I need to understand the exact window of data loss and any potential side effects on related tables. Give me a clear timeline of the deletion event and a report on what other data might have changed since then that I need to be careful not to overwrite.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA critical set of `Finance.Invoices` records has just been reported missing, and I'm under…+
I just discovered a batch of critical `Finance.Invoices` records were deleted, but I'm unsure of the exact time or scope of the deletion.
A critical set of `Finance.Invoices` records has just been reported missing, and I'm under pressure from the finance director to restore them immediately. I don't know the exact time of deletion or how many records are affected. I'm afraid of restoring too much or too little. What's the quickest and safest way to pinpoint the exact deletion event and its scope, then plan a targeted recovery without affecting other recent transactions?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time and causing anxiety for stakeholders during data recovery because I lack a…+
I keep losing time and causing anxiety during data recovery because I lack a clear, immediate understanding of the deletion event's details.
I keep losing time and causing anxiety for stakeholders during data recovery because I lack a clear, immediate understanding of the deletion event's exact timestamp and scope. This delays resolution and erodes trust. What habit should I change to more quickly and accurately diagnose the specifics of a data loss incident, allowing for a faster and more precise recovery plan?
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.