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.

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.

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.

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.