◆ Microsoft SQL Server

Set up automated administration 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 taskSet up a daily backup for the 'SalesData' database, full backup to the 'D:\SQLBackups'…+
Set up a daily backup for the 'SalesData' database, full backup to the 'D:\SQLBackups' directory, retaining backups for 7 days. Schedule it for 2 AM every day, starting tomorrow.
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 set up the automated backups for the new 'CustomerPortal' database, make sure the…+
Before I set up the automated backups for the new 'CustomerPortal' database, make sure the backup process is robust. Configure it to alert me if a backup fails, and ensure the backup location has sufficient space for growth over the next year.
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 automated nightly backups for the 'Inventory' database have been failing for three days,…+
The automated nightly backups for the 'Inventory' database have been failing for three days, but I just found out about it.
The automated nightly backups for the 'Inventory' database have been failing for three days, and I just found out because a user reported data loss. I'm afraid we've lost critical recent data. I can't tell if the previous backups are even valid. What's the likely diagnosis for silent backup failures, and what's the best next move to secure the data and understand the extent of the loss?
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 getting surprised by database issues like full transaction logs or failed backups that…+
I keep getting surprised by database issues that should have been caught by automated tasks.
I keep getting surprised by database issues like full transaction logs or failed backups that should have been caught by automated tasks. My current monitoring is reactive. What habit should I change to shift from reacting to proactive identification and resolution of these routine but critical database administration problems?
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.