Claude on SQL Server FAQ: 7 Questions Teams Ask Me

AI
No Comments

This Claude on SQL Server FAQ collects the questions teams ask me before we set up the loop. My last post, Claude on SQL Server: Read, Prove, Then Change, laid out the loop. Since then, teams have hired me to build it with them. The same seven questions come up in almost every first meeting.

Tilt-shift miniature photo of an antique brass calculating machine inside a glass museum case behind a red velvet rope, with a large magnifying glass looking in without touching it

1. Is It Safe to Let Claude Near Production?

Yes, as long as production only ever sees Claude’s reads. The guardrail is the claude_reader login, not the prompt. It holds VIEW SERVER STATE, VIEW ANY DEFINITION, VIEW DATABASE STATE and SHOWPLAN, and nothing else.

In my test on SQL Server 2025, every SELECT on a table failed with Msg 229. Run the same check with EXECUTE AS LOGIN before you hand the login over.

2. Can Claude See Our Customer Data?

Not the table rows. It can see query text, though, and query text carries values. In my test, the Query Store text of one call showed the date I typed. A literal customer number in a WHERE clause would show up the same way.

So treat the morning reports as internal documents and keep them inside the team. Mask the staging copy where your rules require it. If your work is regulated, bring your compliance person in early, when you decide what Claude can read.

3. We Don’t Have a Staging Server. Can We Still Start?

Yes. Restore last night’s backup to any spare machine with enough disk. Developer edition is free for non-production work, so licensing won’t hold you up.

What you lose is live traffic. A spare box won’t match production’s memory, load or concurrency. That’s why a gain on staging counts as evidence, and Claude checks it held on production the next morning.

Tilt-shift miniature photo of a replica brass calculating machine on a workshop bench with neat tools and a blank notebook, while the original stays in its glass case in the next room

4. How Much of Our Team’s Time Does It Take?

About 20 minutes a day, an hour a week and half a day a month. Daily, someone reads the morning report and picks one or two items. Weekly, the team replays the packs and books a change window. Monthly, they refresh staging and retire old packs.

The first week takes more, because you’re building the login, the staging copy and the first replay pack. After that, the daily part settles into those 20 minutes.

5. What Happens When Claude Is Wrong?

Some findings will be wrong. Every finding comes with a test, so a wrong idea fails on staging, not in production. It still gets a replay pack, so nobody tests the same idea twice.

Each week, note where Claude missed and add a line to its instructions. Some teams also send the same evidence to Codex for a second opinion. When the two disagree, a DBA settles it.

6. Will This Replace Our DBA?

No. Claude gathers evidence and tests ideas on staging. The DBA decides what ships, books the window and keeps the rollback ready. In a real outage, the DBA acts first, because a review step is too slow.

I do raise one warning with every team. A team that approves findings without reading them is building a new risk. Someone has to understand why each fix works.

Tilt-shift miniature photo of a curator's desk at evening with an open blank ledger, a brass key on a wall hook and a warm desk lamp

7. How Soon Will We See a Result?

Aim for one tested fix by the end of the first week. That’s the first stage: one reviewed fix, one replay pack and a morning report someone reads every day. The habit takes a few more weeks to settle.

The bigger payoff comes later, from the past cases library. Before a new investigation, Claude reads past cases that touched the same query or table. New people learn the system by reading it, instead of asking around.

Where to Start

If your team has one hour this week, create the read-only login and test it with EXECUTE AS LOGIN. Everything else builds on that. The full steps are in the first post. You can also hand that post to Claude and let it walk you through. If you’d rather have it running in weeks than months, my consulting page has the details.

I wrote about the risk in question six in Competence Debt: The Line Item No One Tracks. It’s an essay about the skills a team stops building when AI does the work. It’s one of thirty essays in my book AI: Nobody’s in There. But we’re still in here. All of them are free to read online, and the paperback is on Amazon.

The read-only login is not a limit on Claude, it is the reason teams let it in.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.


Discover more from SQL Authority with Pinal Dave

Subscribe to get the latest posts sent to your email.

AI, Best Practices, SQL Performance, SQL Server Security
Previous Post
AI Ran the Query and Returned Wrong Numbers

Related Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.