◆ Microsoft Azure

Troubleshoot continuous database connection errors

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 taskInvestigate the 'inventory-app' service's persistent database connection errors to…+
Investigate the 'inventory-app' service's persistent database connection errors to 'production-db-01'. Check the connection string, firewall rules on the database server, and review database performance metrics for 'production-db-01' to identify any resource contention. Report your findings and a resolution plan by end of day.
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 hand off these 'inventory-app' database connection errors to the DBA team, help me…+
Before I hand off these 'inventory-app' database connection errors to the DBA team, help me gather the most relevant diagnostic data. Focus on connection string validity, network path issues between the app and 'production-db-01', and any recent changes to database firewall rules. I need to present a clear picture of what's already been checked and what's still outstanding.
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 'inventory-app' is throwing 'connection timeout' errors to 'production-db-01', but I can…+
The 'inventory-app' is failing to connect to the database, but the database itself seems fine.
The 'inventory-app' is throwing 'connection timeout' errors to 'production-db-01', but I can connect to the database directly from my machine, and other services are unaffected. I've verified the connection string in the app's configuration. I'm worried it's a subtle network security group rule or a transient DNS issue that's hard to spot. What's the most efficient way to diagnose this specific connection path issue before the business impact escalates, and what's my best immediate action?
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 spending too much time troubleshooting intermittent database connection errors that are…+
I frequently chase down intermittent database connection issues that are hard to reproduce and diagnose.
I'm spending too much time troubleshooting intermittent database connection errors that are tough to pin down, often feeling like I'm grasping at straws. It feels like I'm always reacting. What habit should I change in how I approach monitoring or logging for database connectivity, so I can proactively identify potential issues or at least get better diagnostic data when they inevitably occur, instead of starting from scratch every 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 Azure'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.