◆ Microsoft SQL Server

Archive SQL Server backups

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 taskMove all full database backups older than 90 days for 'ArchiveDB' to the long-term cold storage…+
Move all full database backups older than 90 days for 'ArchiveDB' to the long-term cold storage share on the network, and delete them from local disk.
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 archive the old backups for ArchiveDB, verify that we have a complete and valid chain…+
Before I archive the old backups for ArchiveDB, verify that we have a complete and valid chain of backups in cold storage for the last year. Ensure we can still perform a point-in-time restore if a regulatory audit requires data from last June.
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 move old backups for ArchiveDB to cold storage, but the system says there's not…+
I'm trying to archive old backups, but the storage system is reporting insufficient space, even though it should have plenty.
I'm trying to move old backups for ArchiveDB to cold storage, but the system says there's not enough space, which doesn't make sense given our capacity. The compliance team needs these archived by end of week. I'm afraid of deleting files before they're properly moved. What's the most likely reason for this space error and what should I do to proceed safely?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur backup archiving process is too manual and I often find myself scrambling to free up disk…+
Managing backup retention and archiving is a constant manual effort, prone to errors and storage overruns.
Our backup archiving process is too manual and I often find myself scrambling to free up disk space or verify old backups for compliance. It's a constant drain on my time and a risk for data integrity. What habit should I change to automate and streamline our backup archiving, making it more reliable and less of a headache?
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.