◆ Microsoft SQL Server

Automate SQL Server 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

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 job for the 'MarketingCampaigns' database, storing full backups to the…+
Set up a daily backup job for the 'MarketingCampaigns' database, storing full backups to the 'D:\SQLBackups\Marketing' folder and retaining them for 7 days. I need this running by end of day for the marketing director.
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 the end-of-quarter rush, automate the weekly index rebuild and statistics update for the…+
Before the end-of-quarter rush, automate the weekly index rebuild and statistics update for the 'SalesData' and 'CustomerOrders' databases. This needs to run during off-peak hours, be robust enough to handle failures, and ensure the sales team's Monday morning reports are always fast without manual intervention.
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've been manually running DBCC CHECKDB on our critical databases every week, but it's a huge…+
I've been manually checking database integrity, but it's taking too much time and I'm missing issues.
I've been manually running DBCC CHECKDB on our critical databases every week, but it's a huge time sink, and I'm worried I'll miss a corruption issue that could take down our main application. I need to automate this, but I'm afraid of creating a job that will cripple performance during business hours or fail silently. How can I reliably automate database integrity checks to run efficiently, report errors clearly, and not impact our users during the day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly performing repetitive, manual tasks like checking backups, rebuilding indexes,…+
I spend too much time on repetitive, manual SQL Server tasks that could be automated.
I'm constantly performing repetitive, manual tasks like checking backups, rebuilding indexes, and monitoring disk space, which eats into my time for more strategic work. This reactive approach often means I catch issues too late. What habit should I adopt to systematically identify and automate these recurring database administration tasks, freeing up my time and improving the overall health and reliability of our databases?
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.