◆ Microsoft SQL Server

Perform data cleanup and maintenance tasks

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
See the prompt↓All Microsoft SQL Server tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun a data cleanup task on the 'Logs' table in the 'ApplicationDB' database. Delete all records…+
Run a data cleanup task on the 'Logs' table in the 'ApplicationDB' database. Delete all records older than 90 days. Then, rebuild the indexes on that table.
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 perform the quarterly data cleanup on the 'MarketingCampaigns' database, make it safe…+
Before I perform the quarterly data cleanup on the 'MarketingCampaigns' database, make it safe and efficient. Analyze the impact of deleting old campaign data on reporting, ensure a rollback plan is in place, and optimize the deletion process to minimize transaction log growth.
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 just ran a data cleanup script on the 'CustomerFeedback' database to remove records older…+
I just ran a data cleanup script on the 'CustomerFeedback' database, and now the customer service team says recent feedback records are missing.
I just ran a data cleanup script on the 'CustomerFeedback' database to remove records older than two years, and now the customer service team says recent feedback records from the last six months are missing. I'm afraid I've accidentally deleted current data. I can't tell if the script had a bug or if someone else altered the data. What's the likely diagnosis for this data loss, and what's the best next move to recover the missing records and prevent further damage?
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 encountering situations where data cleanup tasks either miss their target or…+
I keep encountering situations where data cleanup tasks either miss their target or accidentally delete critical information.
I keep encountering situations where data cleanup tasks either miss their target or accidentally delete critical information, leading to data integrity issues and user complaints. My current process for data cleanup is often rushed. What habit should I change to consistently perform thorough, safe, and effective data cleanup and maintenance tasks without causing unintended consequences?
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.