Connect your database to your version control system

Version control schemas and reference data, roll back changes, and maintain the referential integrity of your database. Solve other database challenges like deploying without losing data.

And because it works with the tools you already use, it's an easy setup.

  • Plugs into SQL Server Management Studio
  • Version control your schemas and static data
  • See who made what changes, when, and why
Version control schemas and static data with SQL Source Control

Raise collaboration and productivity

Database version control is hard because there isn’t any source code. Instead, your queries change the state of the database. SQL Source Control solves this problem by scripting each database object into a file in your version control system. This makes it simple for teams to share work and access the history of every single change made to every object in your database.

Whether you work on a shared database or a local, dedicated copy, SQL Source Control helps you share code, avoid conflicts and capture object-level version history, so you can work confidently, without treading on anybody’s toes.

Find out more about SQL Source Control’s key features

Raise collaboration and productivity

Get your databases under version control with Redgate

Includes SQL Source Control and much more to develop and deploy database changes

Flyway Teams

$597 per user*

Ideal for teams with multi-RDBMS estates. Track changes to your schema objects and deploy your database changes with greater speed and accuracy.

SQL Source Control

Plugs into SSMS, providing state-based database versioning for TFS, Subversion and Git


Desktop GUI and CLI providing state-based and migrations-based versioning and deployment capabilities across multiple database systems, including SQL Server, Postgres, Oracle and MySQL

Advanced Flyway capabilities

Add change management controls into your pipeline processes to drive greater precision and accuracy. Includes: dry run, undo migration scripts and cherry pick.

*100 schema limit. Contact us if you need more.

Learn more

SQL Toolbelt Essentials

$1,281 per user

Version control your SQL Server databases and boost team productivity with the industry-standard tools for SQL Server development and deployment.

SQL Source Control

Plugs into SSMS, providing state-based database versioning for TFS, Subversion and Git

SQL Server productivity tools

Industry-leading SQL Server productivity tools, including SQL Compare Pro, SQL Data Compare Pro, SQL Prompt, all designed to standardize and scale development practices across teams

Learn more

Already use SQL Source Control?

If you already own a copy of SQL Source Control or hold a subscription and wish to renew or increase the number of users, please get in touch and we will be very happy to help.

SQL Source Control works with

or any version control system with a command line

Key features of SQL Source Control

Automate SQL changes during deployments

Pre & Post deployment scripts can make SQL changes before and after your deployments. These scripts are managed within SQL Source Control to then be picked up when deploying with other Redgate products.

Learn more about pre & post deployment scripts.

Version control at your fingertips inside SQL Server Management Studio

It's easy to record and share your code changes, because SQL Source Control runs inside SQL Server Management Studio.

You don't have to stop what you're doing or pass round handwritten change scripts.

Version control your schemas and reference data

Store and share any SQL Server object and static data. Committing and updating takes two clicks in the Object Explorer.

To see what’s new, you can check changes down to the individual lines of SQL, with highlighted differences.

View a full history of changes

Look through the full revision history of a database or database object.

You can see who made the changes, when they made them, and why.

Handles referential integrity for you

When you commit or update, SQL Source Control maintains the referential integrity of your database for you.

It works out the right order for your changes and even deals with keys and constraints.

It uses the same engine as SQL Compare, the world’s most trusted tool for syncing database changes.

Push and pull Git repos

Synchronize your local and remote Git repositories inside Management Studio.

Pull down changes from your remote repository, commit your changes locally, and push straight them to your remote repository to share with the rest of your team.

Watch the video.

Roll back any changes you don't want

It's simple to roll back and resolve conflicts from the Object Explorer.

This also gives you a risk-free sandbox. If you want to experiment on your database, go ahead. You can undo any changes you don't want to keep.

Lock objects you're working on

You can lock the object you're working on in SQL Server Management Studio with just one click, so your changes are safe from being overwritten.

Your team can see what's locked, as well as information on who locked it.

Read more about locking in this blog post or watch the video.

Work on a central database or your own local copy

You and your team can work on a shared database or each use a local, dedicated copy.

SQL Source Control supports both models for database development.

Either way, it helps you share code, avoid conflicts, and see who’s doing what, so you can work without treading on each other’s toes.

Exclude objects with filters

If you don't want to share certain objects, such as users or permissions, you can exclude them with filters.

You can exclude objects by type, name, and owner, or specify more complex conditions.

It's simple to share only what you want with your team.

See what's changed, with icons

Icons in the Object Explorer show you when a change has been made to a database by you or your team.

You'll never forget to commit to version control.

How SQL Source Control helps with development and business processes

Deploy your database straight from version control

Avoid errors and stop those 4am deployments

Deploying database changes is nerve-wracking. You have to make certain that nothing breaks and you have to minimize downtime. When something does go wrong, you’re responsible and it can be hard to fix.

So for a lot of us, deployment means queuing up changes, coming in early (or staying late), and crossing our fingers that nothing goes wrong.

SQL Source Control gives you an alternative: deploy from a canonical version of your database in version control. You’re working with a stable version, which cuts the risk of deploying incomplete or incorrect changes.

Deploy from version control using SQL Compare Pro

Deploy straight from your repository

You can make deployments from your repository with SQL Compare Pro, using a manual, state-based approach.

SQL Compare writes deployment scripts in minutes, making your release safe and efficient. You can deploy from SQL Compare or copy the script to review and run later. You can use SQL Compare to generate rollback scripts too.

Harness automation to accelerate the development and deployment of database changes

If you’re already practising continuous integration or continuous delivery for your application changes, you can extend the power of automation to your databases too, using Flyway. With a flexible, hybrid deployment approach, auto-generation of migration and undo scripts, drift detection, reporting and support for multiple RDBMS, Flyway goes further to accelerate software deliver and ensure quality code. Read more about Flyway.

Track progress and pass any audit with a full change history

With SQL Source Control you can keep a full change history for your database and every object in it.

It shows you who made changes, when they made them, and why. You stay up to date with progress and you get complete oversight of the changes that go into production.

Pass any audit and prove regulatory compliance

A well-documented change management process is also essential to win the trust of auditors or investors.

With a complete record of development changes in SQL Source Control, you can pass audits and prove you comply with standards such as Sarbanes-Oxley or HIPAA.

“If we can prove we can track the entire history of our data’s lifecycle, we’ll pass any audit. If not, we face massive fines, legal charges, suspension from trading, and possible termination of the company. Faced with that, how could I afford not to source control my database? How could anyone?”

Lynton Mack, DBA, Cameco Corporation

Keep an eye on database changes and know who changed what and when

Without version control, it’s almost impossible to keep track of development. As teams are growing, it becomes more and more complex to check on progress and work out what work your team has completed. How did your database reach its current state? Who just broke the build – and how are you going to fix it?

With SQL Source Control you’ll know exactly who made changes, when they made them, and why. You stay up to date with progress and you get complete oversight of the changes that go into production.

“Yesterday a vendor made a change to our database which broke some customer extracts.

With SQL Source Control, I was able to find exactly what the problem was and fix it in minutes.”

Scott Kowalczyk, Georgia Central Credit Union

How SQL Source Control versions your database objects

Database version control is hard because there isn’t any source code. Instead, your queries change the state of the database.

SQL Source Control solves that problem by scripting each database object into a file in your version control system.

It’s possible to do this with an elaborate manual workaround, but SQL Source Control makes it easy for you in three ways:

  1. You don’t need to leave SQL Server Management Studio – you can do it all with a few clicks in the Object Explorer.
  2. You don’t need to remember to script out your files or instil that habit in new team members. SQL Source Control highlights your changes in the Object Explorer, so you see what’s sitting outside version control at a glance.
  3. You don’t have to worry about referential integrity or data persistence. SQL Source Control sorts out the order of your changes and deals with keys and constraints for you. With migration scripts, you can specify how to deal with complex changes that affect your data, such as table splits.

When you’ve made your changes, you check them in with a couple of clicks, just like you would for your application code. SQL Source Control scripts out files that represent the new state of each object and saves them in your version control system.

Not only is it simple to share your work – you also have a history of every change to every object in your database, along with details of who made each change, when, and why.

“Before using SQL Source Control, we'd tried a whole bunch of things. Sometimes we passed around manual backups, or SQL CREATE scripts, but that meant only one developer could work on the database before we had to issue updates again. We tried Database projects in Visual Studio, but they were clunky, and rather fragile when we made substantial changes.

One of our developers eventually cooked-up his own sync tool. It was a time consuming project. We had to teach new developers how to use it, enforce certain conventions, and it only really worked when source and target could be accessed at once, which wasn't often.

SQL Source Control did everything that sync tool could do, without wasting time or causing frustration...Integration with SSMS and TFS saved us a lot of hassle, but the major benefit has been the time it’s saved us making and pushing database changes. I'm not sure I could give that up again.”

Phil Gale, Red Jungle
Read more