◆ Microsoft SQL Server

Manage SQL Server transaction logs

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 taskPerform a transaction log backup for the 'SalesData' database on 'DBHOST04' immediately, then…+
Perform a transaction log backup for the 'SalesData' database on 'DBHOST04' immediately, then truncate the log to free up space, ensuring the backup is stored in the 'D:\SQLBackups\SalesData' directory.
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 we start the large data import into the 'ArchiveDB' database tonight, I need to ensure…+
Before we start the large data import into the 'ArchiveDB' database tonight, I need to ensure its transaction log won't fill up and halt the process. Can you analyze the current log growth rate and recommend the optimal log file size and backup frequency for the duration of the import, which is expected to take six hours?
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 transaction log for the 'CustomerOrders' database on 'PROD_SQL_02' has grown to 95% full,…+
The transaction log for the 'CustomerOrders' database has grown to 95% full and is causing write operations to fail.
The transaction log for the 'CustomerOrders' database on 'PROD_SQL_02' has grown to 95% full, and new orders are failing to write, impacting live sales. I've tried a quick log backup, but it's still critically full. I'm afraid of losing data if I just shrink it without understanding why it grew so fast. The sales team is panicking. What's the most likely diagnosis for this rapid growth, and what's the safest immediate action to free up space without data 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'm constantly reacting to full transaction logs across various production databases, leading…+
I'm constantly reacting to full transaction logs, leading to emergency backups and shrinking.
I'm constantly reacting to full transaction logs across various production databases, leading to emergency backups and shrinking operations that disrupt business. This reactive approach wastes time and increases stress. What habit should I change to proactively manage transaction log growth and prevent these critical space issues before they impact operations?
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.