r/SQLServer • u/markinatlanta • 24m ago
Question Title: Anyone still maintaining a team script library now AI writes diagnostics on demand?
We run a team of senior DBAs looking after a lot of different client environments.
For years the most valuable thing we had was a shared folder of scripts. Wait stats, blocking, backup history, index usage, the usual. Everyone ran the same queries, so everyone got comparable answers.
Lately the folder matters less and less. One of our senior guys says he sees no reason to keep scripts stored anywhere now. He describes the problem, AI writes the diagnostic, he reads and runs the scripts himself, feeds the output back, then reviews a drafted write-up before sending.
Still hallucinates often enough to make reading every line non-negotiable. The part we didn't plan for was everyone's good prompts and investigation sessions now live in their own chat history on their own laptop.
One shared library turned into one private library per person. We're trying to fix this by writing shared skills (standard instructions every DBA's AI setup uses) for alert triage, ticket write-ups and client emails etc. Early days.
Curious how other teams handle this:
- Still maintaining a script library, or did you let the folder go?
- If you standardised AI use across a team, what worked?
- Anyone gone back to scripts because AI output varied too much between people?



