AI for SSMS, compared — SQL Sage vs GitHub Copilot vs SsmsAgentic
Three ways to put AI inside SQL Server Management Studio 22 today. They overlap on chat and T-SQL help, so this page is precise about where they actually differ — and honest about where the others match us. SQL Sage details come from our own product; competitor details from their public documentation (see Sources). No invented weaknesses.
On this page
01The choice today
If you work in SQL Server Management Studio 22 and want an AI assistant next to your query editor, there are three distinct options as of August 2026:
- GitHub Copilot in SSMS — Microsoft's first-party assistant, installed via the Visual Studio Installer (the “AI Assistance” workload). You sign in with a GitHub account that has a Copilot subscription; the model is provided by GitHub Copilot.
- SsmsAgentic — an independent AI pair-DBA panel that brings Claude into SSMS 22. Per its README it launches the Claude Code CLI as a child process, is keyless, shows an Allow/Deny banner per statement, writes a full audit log to disk, and offers a 15-day trial.
- SQL Sage — an independent AI pair-DBA that runs on the Claude or ChatGPT/Codex account you already have (keyless) or your own key (BYOK, no CLI). It adds a Proven & Accountable layer the other two do not document: deterministic blast-radius before ALTER/DROP, a proof that an AI rewrite returns the same rows, one-click incident triage from live DMVs, and a tamper-evident audit log you can export as evidence.
SQL Sage and SsmsAgentic are genuinely close on the fundamentals — both independent, both keyless via the Claude Code CLI, both classify statements and confirm writes, both keep an audit log. So the honest question isn't “who has a CLI” — it's which model do you want to run, and do you need the changes proven and logged as evidence. The table below sticks to what each vendor documents publicly.
02What SQL Sage is — and isn't
What it is
- A full AI pair-DBA inside SSMS 22 — chat in the context of your active query window and connection
- Writes, explains, optimizes, fixes and documents T-SQL; right-click editor actions; optional inline completions
- Multi-provider: Claude and ChatGPT/Codex
- Deterministic DBA tools — Query Store, waits, blocking, deadlocks, missing indexes, execution plans
- A proof-and-audit layer on top of all of it
Who it's for
- DBAs and SQL developers who touch production and want changes proven before they run
- Teams that must show what the AI did and who approved it (change control, on-call, audits)
- People who want to use the Claude or ChatGPT account they already pay for — no GitHub, no Copilot licence
- Orgs where GitHub is blocked by policy but an AI assistant is still wanted
Who it's NOT for
- If all you want is ghost-text autocomplete in the editor, a general assistant like Copilot fits better — SQL Sage's completions are an opt-in extra, not the point
- If you specifically want Microsoft's first-party tool and already pay for Copilot
- If you'll never run a write or a schema change and never need an audit trail, the proof layer is wasted on you
We'd rather tell you where it doesn't fit than oversell it. If the proof-and-audit layer below doesn't matter to your work, one of the other two may serve you just as well — and the table says where they win.
03The difference: proof & accountability
Everything above the line — chat, T-SQL help, DBA tools — SQL Sage and SsmsAgentic both do, and Copilot does the general-purpose version. The reason to reach for SQL Sage is what it does below the line. Its own tagline: Copilot guesses; SQL Sage proves it — and logs it.
- Change-Impact — prove the blast radius before you
ALTERorDROP. It reads the system catalogs and reports the dependent views, procedures, functions, triggers and constraints, the inbound foreign keys, the rows at risk and the object's indexes — deterministically, not guessed. Honest limit: static analysis cannot see dynamic (EXEC/sp_executesql) or cross-database SQL, and it says so. - Prove-It — proof that an AI rewrite returns the same rows. A deterministic, server-side multiset fingerprint (order-independent and duplicate-aware) plus the logical-reads delta, with a clear EQUIVALENT / DIFFERENT / UNDECIDABLE verdict. It runs read-only in a rolled-back transaction, costs zero AI tokens, and is honest when a query genuinely can't be proven (a nondeterministic function, or
TOPwithoutORDER BY). - Incident Mode — on-call triage that cites the proof. One click runs a deterministic, read-only snapshot of what the server is doing right now — the blocking chain, top waits with each one's % share, and the most expensive in-flight queries — every number cited from a live DMV, never guessed. Reads server state only, never table data.
- Tamper-evident audit log + evidence pack. Every AI action is recorded to a local, hash-chained audit log, so an edit, deletion or reorder of any entry still in the file is detectable (SHA-256 chain). Export an evidence pack in Markdown + JSON — what the AI did to production and who approved it — with a one-line integrity verdict. (Honest scope: a bare append-only chain can't prove the newest lines weren't dropped from the end — it's a tamper-evidence aid, not a certified immutable compliance record.)
- Evidence-first, not guess-first. The assistant grounds claims in real catalog and DMV values rather than asserting them, and states plainly when something is dynamic, cross-database or otherwise unresolved instead of glossing over it.
- Connect a repository (preview). Opt-in, per repository, on the Claude channel: the assistant reasons about your application's source code alongside the database. Native file, shell and search tools are disabled while a repo is connected — it sees only a filtered, secret-free copy through SQL Sage's own read/search tools, never your live disk; secret files are excluded before anything is sent and the copy is deleted on disconnect.
Neither GitHub Copilot in SSMS nor SsmsAgentic describes an equivalent proof-and-equivalence layer in its public documentation. SsmsAgentic does keep an audit log — we don't claim otherwise — but its site does not describe it as tamper-evident or as an exportable evidence pack. Where their docs are silent, the table marks the cell “—” rather than guessing.
04Full comparison table
| SQL Sage | GitHub Copilot in SSMS | SsmsAgentic | |
|---|---|---|---|
| Runs in | SSMS 22 (Windows) — independent extension | SSMS 22 — Visual Studio Installer (“AI Assistance” workload) | SSMS 22 — independent extension / chat panel |
| Setup / account | Keyless (your Claude or ChatGPT/Codex account) or BYOK (your own key, no CLI) | GitHub account with a Copilot subscription | Keyless via the Claude Code CLI (your Claude account) |
| AI providers | Claude and ChatGPT / Codex | Model provided by GitHub Copilot | Claude only (no other provider stated) |
| Needs a separate API key? | No (keyless); optional Anthropic BYOK key, encrypted with DPAPI | No — sign in with GitHub | No — keyless via Claude Code |
| Requires a background CLI process? | Only on the keyless path; BYOK needs no CLI | — (not stated) | Yes — launches the Claude Code CLI as a child process |
| Read-only by default + confirm writes/DDL | Yes — ScriptDom parser gate; exact SQL shown before writes/DDL | — (not stated in public docs) | Yes — Allow/Deny banner per statement; writes highlighted |
| Local audit log | Yes | — (not stated in public docs) | Yes — full audit log written to disk |
| Tamper-evident audit + evidence-pack export | Yes — SHA-256 hash chain; export Markdown + JSON | — (not stated) | — (audit log present; not stated as tamper-evident / exportable) |
| Deterministic blast-radius before ALTER / DROP | Yes — dependents, inbound FKs, rows & indexes from the catalogs | — (not stated) | — (not stated) |
| Proves an AI rewrite returns the same rows | Yes — deterministic multiset, keyless | — (not stated) | — (not stated) |
| Reads your application repo code | Preview — opt-in, per repo, Claude channel | — (database only) | — (not stated; database-focused) |
| Telemetry / token custody | Minimal opt-in telemetry; no token custody (DPAPI) | — (see Microsoft's terms) | — (not stated) |
| Free trial | 30-day, no credit card | Copilot Free tier (not a time-limited trial) | 15-day, no card (clock starts on first opening the chat pane) |
| Best-fit user | Production DBA work that must be proven & logged; your own Claude/ChatGPT account | Already pay for Copilot; want Microsoft's first-party assistant | Want a Claude pair-DBA in SSMS via one-time purchase |
05Setup — keyless, BYOK, and the CLI
There's a common misconception worth clearing up: that one of these tools is “the simple one with no CLI”. In fact both SQL Sage's keyless path and SsmsAgentic use the Claude Code CLI. The real setup difference is that SQL Sage gives you a second path that needs no CLI at all, plus a second provider.
- SQL Sage — keyless. Signs in with the Claude or ChatGPT account you already pay for, through Claude Code or the Codex CLI. On this path SQL Sage never sees, stores, or transmits your credentials; it only asks the CLI whether you're signed in. No API key, no GitHub account, no Copilot licence.
- SQL Sage — BYOK (no CLI). Prefer not to run a CLI? Paste your own Anthropic API key and SQL Sage talks to the API directly — no Claude Code, no background process. The key is the one secret it keeps, stored on your machine encrypted with Windows DPAPI.
- GitHub Copilot in SSMS. Installed through the Visual Studio Installer's “AI Assistance” workload; you sign in with a GitHub account that has a Copilot subscription. The model comes from GitHub Copilot rather than a Claude/ChatGPT account you connect. (For context, the earlier “Copilot in SSMS 21” used your own Azure OpenAI endpoint, deployment and API key; that was replaced by GitHub Copilot in SSMS 22.)
- SsmsAgentic. Per its README, it launches the Claude Code CLI as a child process and is keyless via that CLI's authentication, reusing your live SSMS connection. It is Claude-only.
06Providers & choice
If it matters which model answers, the options differ:
- SQL Sage supports both Claude (via Claude Code) and ChatGPT / Codex (via the Codex CLI), and you pick a model from a dropdown; new Claude and ChatGPT/Codex models appear in the picker without a plugin release.
- GitHub Copilot in SSMS provides the model through GitHub Copilot — you sign in with GitHub rather than connecting your own Claude or ChatGPT account.
- SsmsAgentic brings Claude to SSMS; support for other providers is not stated on its site.
07Safety, privacy & telemetry
Here we speak in detail about SQL Sage, because that's the product whose internals we can state as fact. For the others, where their public documentation doesn't spell out the equivalent behaviour, the cells above are marked “—” rather than guessed at. Where SsmsAgentic's README does state a behaviour (per-statement Allow/Deny, an audit log to disk), we credit it as fact.
In SQL Sage:
- Read-only by default. Statements are classified by the same parser SSMS uses (ScriptDom). SELECT runs read-only; DML and DDL require a confirmation dialog showing the exact SQL before anything executes — every time. Safety is a feature here, not friction: only destructive operations stop for you.
- Your data stays yours. Schema metadata and your query text go to the model; query result rows never do, unless you opt in per session. Server and database names can be masked. An egress panel shows the exact payload before it is sent.
- Local, tamper-evident audit. Every operation performed or blocked is appended to a local, hash-chained JSONL log under
%LOCALAPPDATA%\SqlSage\audit\— local-only, no network egress — exportable as an evidence pack. - No token custody. On the keyless path, sign-in lives in Claude Code / Codex; SQL Sage never holds your account credentials. With BYOK, the one secret is your key, encrypted with DPAPI. Secrets are never in plaintext, the registry, or version control.
- Minimal, opt-in telemetry. Product telemetry is minimal and opt-in — it is not required for the tool to work.
If any of the other tools document the same guarantees, treat their own docs as the source of truth — we don't claim what we can't verify, and we don't claim they lack what they simply don't mention.
08Updates & releases
A second misconception worth correcting: that an independent extension means rare, manual updates. SQL Sage ships frequently and updates itself — new builds are delivered through built-in auto-update, with no manual reinstall. The model list updates independently too: new Claude and ChatGPT/Codex models show up in the picker without waiting for a plugin release, because the list is fetched from a hosted manifest.
09FAQ
Does SQL Sage require the Claude Code CLI?
Only on the keyless path. Keyless sign-in drives the Claude account you already have through Claude Code, or your ChatGPT/Codex account through the Codex CLI — so on that path the CLI is required. If you prefer, use BYOK instead: paste your own Anthropic API key and SQL Sage talks to the API directly, with no CLI and no background process. Either way there is no separate GitHub or Microsoft account, and no Copilot licence.
Is SQL Sage only for audits or only for DBAs?
No. SQL Sage is a full AI pair-DBA: it chats in the context of your active query window and connection, and helps you write, explain, optimize, fix and document T-SQL, with right-click editor actions and optional inline completions. The proof-and-audit features (blast-radius before ALTER/DROP, prove-equivalence, incident triage, the tamper-evident audit log) are what set it apart, but they sit on top of everyday query-writing help — they are not the whole product.
How is SQL Sage different from GitHub Copilot in SSMS?
GitHub Copilot in SSMS is Microsoft's first-party, general-purpose assistant: you install it through the Visual Studio Installer's AI Assistance workload and sign in with a GitHub account that has a Copilot subscription; the model is provided by GitHub Copilot. SQL Sage is an independent extension that runs on the Claude or ChatGPT/Codex account you already have (keyless) or your own key (BYOK). Its differentiator is a Proven & Accountable layer that Copilot's public docs do not describe: deterministic blast-radius before ALTER/DROP, a proof that an AI rewrite returns the same rows, one-click incident triage cited from live DMVs, and a tamper-evident, hash-chained audit log you can export as an evidence pack.
How is SQL Sage different from SsmsAgentic?
They are close on the basics — both are independent SSMS 22 extensions, both are keyless via the Claude Code CLI, both classify statements and ask before writes, and both keep an audit log. Per its own README, SsmsAgentic is Claude-only, shows an Allow/Deny banner per statement with writes highlighted, writes a full audit log to disk, and offers a 15-day trial. SQL Sage adds three things SsmsAgentic's site does not describe: a Proven & Accountable layer (deterministic blast-radius, prove-equivalence, incident triage, and a tamper-evident hash-chained audit log with evidence-pack export), a second provider (ChatGPT/Codex as well as Claude) with an optional CLI-free BYOK path, and connect-a-repository preview so the assistant can reason about your application code alongside the database. It also has a 30-day trial.
Does SQL Sage send my data to the AI?
Schema metadata and your query text go to the model; query result rows never leave your machine unless you opt in per session. Server and database names can be masked. An egress panel shows the exact payload before it is sent. On the keyless path SQL Sage never sees, stores, or transmits your credentials — sign-in lives in Claude Code / Codex. With BYOK, your key is the one secret it keeps, stored encrypted with Windows DPAPI. Telemetry is minimal and opt-in.
Is SQL Sage safe to run against a production database?
It is read-only by default. Statements are classified by the same parser SSMS uses (ScriptDom): SELECT runs read-only, while DML and DDL require a confirmation dialog showing the exact SQL before anything executes. Before an ALTER or DROP, Change-Impact reports the deterministic blast radius from the system catalogs. Every operation performed or blocked is appended to a local, hash-chained JSONL audit log with no network egress, which you can export as an evidence pack.
How often is SQL Sage updated?
Frequently, with built-in auto-update — new builds are delivered without a manual reinstall. The model list also updates on its own: new Claude and ChatGPT/Codex models appear in the picker without waiting for a plugin release.
Do I need a separate API key for SQL Sage?
No. SQL Sage is keyless — it signs in with your own Claude or ChatGPT account through Claude Code or the Codex CLI. Advanced users can optionally paste their own Anthropic API key (BYOK), stored encrypted with Windows DPAPI, but it is not required for chat, query help or safe execution.
10Which should you pick?
All three run in SSMS 22, so it comes down to fit:
- Pick SQL Sage if you touch production and want changes proven and logged as evidence — deterministic blast-radius, prove-equivalence, incident triage, a tamper-evident audit log — on the Claude or ChatGPT/Codex account you already have, keyless or with a CLI-free key.
- Pick GitHub Copilot in SSMS if you already have a GitHub Copilot subscription and want Microsoft's first-party assistant installed through the Visual Studio Installer, and general-purpose ghost-text completions matter most.
- Pick SsmsAgentic if you specifically want a Claude pair-DBA in SSMS with per-statement approval and are happy with Claude only.
Want the SQL Sage detail on keyless sign-in and what each provider gives you? See your own AI account in SSMS — Claude or ChatGPT/Codex, or the full documentation. Every install starts a 30-day free trial with all features, no credit card.
11Sources & disclaimer
- GitHub Copilot in SSMS — Microsoft Learn, “Install GitHub Copilot in SSMS”: learn.microsoft.com/en-us/ssms/copilot/copilot-in-ssms-install
- SsmsAgentic — vendor site: ssmsagentic.io and its public README: github.com/ado-webco/ssms-agentic
SQL Sage facts on this page reflect the current product; see the documentation and home page for the authoritative description.