As part of my wider work exploring Claude Code and AI-assisted database engineering, I have been looking at how AI can support SQL Server operations.

A failed job, missed backup, full transaction log or blocking issue can quickly become business-critical. In that environment, AI needs more than good answers. It needs control.

Personally there are 4 keys things I look for when designing database centric agents.

Evidence Before Opinion

Generic AI can explain SQL concepts, but real triage needs evidence:

• What was checked?
• What was found?
• How confident is the result?
• Did it just make something up ?
• How did it get to the conclusion?

Without evidence, AI becomes another source of risk and uncertainty, DBAs don’t like either.

Guardrails Before Automation

A proper database agent should work through approved diagnostic paths, controlled tools and clear boundaries.

Early systems should focus on read-only checks, structured outputs, validation and human review. Do I really want a fully agentic agent with sub agents loose on my live systems ? Nope !

Audit Trails Build Trust

For enterprise teams, auditability is essential.

Every diagnostic step, tool call, result and recommendation should be traceable. So if the agent tells me that my recovery pending database isn’t that bad of an issue I want to know why it thinks that. I want to see its thinking process and its end conclusion.

The Human Stays in Control

AI should not replace DBAs. It should help them reduce noise, triage faster and focus on higher-value decisions. Who knows in the future but right now, I have the final say not Claude.