◆ Microsoft SQL Server

Resolve SQL Server error 53

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 taskIdentify all active connections to the 'InventoryDB' database from a client machine with IP…+
Identify all active connections to the 'InventoryDB' database from a client machine with IP address '192.168.1.100'.
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 block access, give me more context on the connections from '192.168.1.100' to…+
Before I block access, give me more context on the connections from '192.168.1.100' to 'InventoryDB'. Show me the programs they are running, the last command executed, and how long each connection has been idle. Highlight any connections that have been open for more than 2 hours or are running suspicious commands.
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 seeing multiple active connections to our 'CustomerDataProd' database from an external IP…+
I'm seeing multiple connections to 'CustomerDataProd' from an external IP that shouldn't have access, and I can't identify the user.
I'm seeing multiple active connections to our 'CustomerDataProd' database from an external IP address, '203.0.113.45', that is not on our approved list. The connections are using a generic application login, making it hard to identify the actual user. This feels like a security breach, and I'm afraid of data exfiltration. What's the most likely scenario for this unauthorized access, and what's the immediate action I should take to contain it without disrupting legitimate users?
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 discovering unauthorized or suspicious connections to our critical databases,…+
I keep discovering unauthorized or suspicious connections to our databases after the fact.
I'm constantly discovering unauthorized or suspicious connections to our critical databases, like 'HRDataProd', after they've already been established for some time. This reactive discovery puts sensitive data at risk and causes panic. What habit should I change to proactively monitor and alert on unusual connection patterns or attempts, so I can detect and respond to potential breaches in real-time?
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.