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.
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.
Ten essential SQL Server tools for releases and productivity
Any questions?
per user/year
Version control your SQL Server databases and boost team productivity with the industry-standard tools for SQL Server development and deployment.
Considering a longer-term contract?
Ask us about available discounts
Plugs into SSMS, providing state-based database versioning for TFS, Subversion and Git
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
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.
or any version control system with a command line
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
You can make deployments from your repository with SQL Compare, 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.
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 Redgate Flyway. With a flexible, hybrid deployment approach, auto-generation of migration and undo scripts, drift detection, reporting and support for multiple RDBMS, Redgate Flyway goes further to accelerate software deliver and ensure quality code. Read more about Redgate Flyway.
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.
Read more
