Who changed this stored procedure?
The proc is broken. It worked yesterday. Three people had access. The change isn't in any ticket. You're reading server logs to find out who touched what.
DBA · Tuesday 09:21
Avesys SQL Version Control · Available now
Treat your database schema like the code it actually is.
SQL Version Control lives inside SSMS — the tool your DBAs already use — and brings Git-grade change tracking, history, and team workflows to SQL Server schema. Without forcing anyone to learn a new IDE.
Built for
SQL Server 2016+SSMS extension14-day free trialGitHub · GitLab · Azure DevOps · Bitbucket · self-hosted
The problem · sound familiar?
The application code is reviewed. The schema is on its honour.
Three questions that come up on every release week — and the kind of answers your team is forced to give without proper tooling for the database.
What's actually in production right now?
You have the schema in source control. You have the schema in production. They diverged six months ago. Now every deployment is a guess about what's already there.
Lead DBA · pre-release call
We use Git for the app. Why is the database still a free-for-all?
Developers branch, review, and merge their application code daily. The database that the application runs on is still edited by hand, in SSMS, with no review and no history.
Engineering manager · retro
What SQL Version Control does
Every schema change, attributed and reviewable.
A Git workflow for SQL Server schema — without leaving SSMS. Commit, review, merge, and roll back. The audit trail is automatic. The Git provider is whichever one you already have.
No new IDE. No context switch.
SQL Version Control plugs into SQL Server Management Studio — the tool your DBAs and database developers already have open all day. Commit, review, and roll back schema changes without leaving the environment you work in.
09:42dbo.sp_GetCartmarcoEdit
09:43— (staged)marcoStage
09:46— (commit a4f9c2e)marcoCommit
09:46→ origin/feat/promomarcoPush
10:12PR #218 openedmarcoReview
Who · what · when · why. Automatically.
Every object — tables, views, procedures, functions, indexes, triggers — versioned, attributed, and timestamped. See who changed what, when, and why. No more reading server logs to reconstruct the history.
main release-4 cut
b81a7d3
feat/promo sp_GetCart · +PromoCode FK
a4f9c2e
feat/promo review · sara approved
7d3e891
main merge feat/promo → main
f55b1c0
main tag release-4.2
2a89f04
Works with the Git you already have
One database. Any Git provider.
Integrates with your existing Git provider. The database lives in the same repos as the application code, or in its own. Your call.
● GitHub ● GitLab ● Azure DevOps ● Bitbucket ● Self-hosted Git
Who it's for
Built for the teams accountable for schema change.
If a database change can break your week, SQL Version Control is for you.
Database developers
Want their schema work reviewed and shipped the same way their application code is — branches, PRs, attribution, the works.
DBAs on the hook
Need a real audit trail of who changed what — and the ability to roll back when something goes wrong, without writing forensics scripts at 2 AM.
DevOps & release teams
Building database deployment into a real release pipeline — not a manual checklist held together by tribal knowledge and Slack threads.
Compliance-bound orgs
That need provable, attributable schema change history — for SOC 2, ISO 27001, internal audit, or the auditor on the phone next quarter.
Why Avesys SQL Version Control
Built around SSMS, not around itself.
Other database version control tools force a workflow shift. Avesys meets your team where they already work. If they can write a stored procedure, they can version one.
SQL Version Control runs inside your network, alongside the databases and the Git provider it connects to. We've reverse-engineered who changed what at 2 AM. We've rebuilt schemas from log files. The product reflects that.
01
On-premise from day one
Like every Avesys product, SQL Version Control runs inside your network. Your schema, your history, your Git provider — your choice. Nothing routed through a SaaS in the middle.
02
Part of the Avesys platform
One vendor for monitoring (DPM), comparison (Database Compare), and version control. One operational model. One license portal. One team to call when something matters.
03
Designed by people who've shipped bad migrations
The commit flow, the rollback path, the audit trail — all shaped by DBAs and developers who've lived through the 2 AM Slack thread, not by a UI team guessing at the workflow.
SQL Server
Schema source of truth
SSMS + Avesys VC
Stage · commit · review
Your Git Provider
GitHub · GitLab · ADO · Bitbucket · self-hosted
Outbound to Avesys SaaS✕ No schema · no history · no telemetry leaves the network
Air-gap capableYour Git, your historySame model as DPM & DBC
How it works
Four steps. From SSMS to merged.
From "I changed a proc" to "the change is in main, attributed, reviewed, and ready to deploy" — in a workflow your team already knows.
Install & connect
Install the SSMS extension. Connect your databases. Connect your Git provider. No agents on the SQL Server, no separate IDE.
⏱ ~10 minutes
Commit as you work
Edit schema in SSMS as you always have. Stage your changes — or capture changes already made by others. Commit with a message that explains why.
⏱ Inline with normal work
Review & merge
Push to a branch. Open a pull request in the Git provider your team already uses. Get the change reviewed. Merge when it's ready.
⏱ Your normal PR cycle
Deploy with visibility
Generate migration scripts from the merged branch. Review them. Run them on the next environment — manually or through your CI/CD pipeline.
⏱ On your release schedule
Try it free
See it inside your SSMS before you decide.
The full product, in your environment, with your databases — for 14 days. No credit card. No commitment. When the trial ends, talk to our team about a license if it's right for you.
14-day free trial
Everything in the product. None of the friction.
14 · days
No credit card · no commitment
→The complete SSMS extension — every feature, on day one
→Connect unlimited databases and Git repositories
→All Git provider integrations enabled
→Direct email support from our engineering team
What we don't do
No drip campaign. No sales pressure.
✕We don't auto-charge you on day 15
✕We don't ask for a credit card to start
✕We don't hold your Git history hostage — it's in your repo, on your provider
✕We don't drop you into a marketing automation sequence
✓If you want to talk, we're a 20-minute call away
Pricing
Simple, predictable, per-seat.
Priced for the people who actually use the product, not the database instances they connect to. No tiers. No add-ons. No surprise renewal math.
Avesys SQL Version Control · per user, per year
€150
One number. Everyone who commits, pays it.
€150 per user, per year — that's the whole price list. Volume discounts available for larger teams; talk to us. Existing Avesys DPM customers can roll SQLVC into the same license relationship.
Full SSMS extension functionality
Unlimited databases, unlimited Git repositories
All Git provider integrations
Updates and new features through your license term
Email support from the engineering team
14-day free trial · no credit cardTry it
Command-line / automation for CI/CD
Already on DPM? Bundle into one license relationship.
How to get started
Two paths. Pick the one that fits.
Some teams want to see the product in their own environment before a conversation. Others want to talk first. Both are fine.
Start your 14-day free trial.
Install the SSMS extension. Connect a database. Connect your Git provider. See it work in your environment, with your schemas — no credit card, no sales call required.
Start free trial →~10 min to first commit
Book a 20-minute call.
For volume pricing, procurement support, security review, or platform bundling with DPM and Database Compare — talk to our team directly. No discovery deck. No qualification ladder.
Book a demo →Reply within 1 business day
Frequently asked
FAQ — the honest answers.
The questions procurement, security, and the DBA team usually arrive with on the first call. Same answers we give them.
Q · 01
What does it cost?
€150 per user, per year. Volume pricing available — talk to our team. No per-database or per-instance fees. No add-on modules.
Q · 02
Is there a free trial?
Yes. 14 days, no credit card required. The full product, in your environment. We don't auto-charge you when the trial ends — if you want to keep going, you talk to us.
Q · 03
Is it a standalone application?
No. SQL Version Control is an SSMS extension. It runs inside the tool your team already uses. No separate IDE, no agents on the SQL Server.
Q · 04
What Git providers does it support?
GitHub, GitLab, Azure DevOps, Bitbucket, and self-hosted Git. If you have a working Git endpoint over HTTPS or SSH, it'll connect.
Q · 05
Does it work without internet access?
Yes. SQL Version Control follows the same on-premise design as the rest of the Avesys platform. It works with on-prem Git installations and in air-gapped environments.
Q · 06
What SQL Server versions are supported?
SQL Server 2016 and later. Windows and Linux hosts. Same workflow on either platform.
Q · 07
How does it work with Avesys Database Compare?
They complement each other — Database Compare handles environment-to-environment diffing, SQL Version Control handles change history and team workflow. Use either independently or together.
Q · 08
Will it integrate with my CI/CD pipeline?
Yes — command-line and automation support is included. Migration scripts generated by SQLVC plug into whatever release pipeline you already run.
Q · 09
What happens to my history if I uninstall?
Your Git history is in your Git repo. Avesys doesn't hold your version history hostage. Uninstall the extension and your repo is unchanged.
Q · 10
How do I buy?
Talk to our team. We'll handle pricing, licensing, and procurement support. Self-serve checkout is on the roadmap — for now, every order goes through a person.
Try it for yourself
The database deserves the same care as the code that runs on it.
Install the SSMS extension, connect a database, connect Git — 14 days, no credit card.