SQL Source Control 5

SQL Source Control 5.3 release notes

Before you update, here are a few things you should know:

The new migrations solution replaces all previous versions

Migration scripts created using previous versions of SQL Source Control won't be compatible with SQL Source Control 5. To make sure any existing migration scripts aren't lost, see Upgrading from old versions of migration scripts before you update to SQL Source Control 5.

To deploy SQL Source Control 5 migration scripts using SQL Compare, you'll need SQL Compare version 11.6 or greater.

The following version control systems are no longer supported:

The following SQL Server versions are no longer supported:

  • SQL Server 2005 (RTM, SP1, SP2, SP3 and SP4).

5.3.7 - December 14th, 2016



  • Fixes the issue introduced in 5.3.6 which caused SQL Compare to fail when SQL Source Control is installed
  • SC-9136: SQL Source Control now correctly handles stored procedure parameters with negative defaults
  • It is no longer possible to perform any other operations when there is a comparison options change to commit or retrieve. You are always required to deal with the comparison options change first. This prevents failures when retrieving migration scripts and other changes that might be affected by the comparison options.

5.3.6 - December 7th, 2016


Note - this version of SQL Source Control was withdrawn because it introduced a regression. After upgrading to this version, you get an error while trying to use SQL Compare with Source Control selected either in Source or Target.

5.3.5 - November 23rd, 2016



  • Support for create, alter and drop EXTERNAL RESOURCE POOL syntax in SQL Server 2016
  • Support for the CONTAINMENT = NONE/PARTIAL syntax in SQL Server 2016
  • Support for SELECT statements using the FROM OPENJSON (...) WITH syntax


  • Object changes already covered by an uncommitted migration script no longer display on the migrations tab
  • SOC-8206: Checkbox selections are no longer lost when an error occurs on the Get Latest tab
  • SOC-8273: Warnings on indexes no longer prevent changes being committed to source control
  • SOC-8087: Migrations no longer crash if Git is not installed
  • SDC-2176: SQL Source Control will no longer insert/update static data rows in multiple batches of 8000 bytes
  • SC-9117: SQL Source Control no longer errors when several Windows users with the same name but different domain names exist in the same database
  • SC-9112: SQL Source Control now successfully compares user defined types named "TableType" between a database and script folder
  • SC-9090: SQL Source Control now detects the dependency between a computed column in a table and the function

  • SQL Source Control no longer fails with the error "The string was not recognized as a valid DateTime..." when trying to commit or retrieve (regression introduced in version 5.3.4)
  • SC-9134: SQL Source Control no longer errors when comparing Windows users that differ in case when the case-sensitive object definition option is set

5.3.4 - November 18th, 2016


Note - this version of SQL Source Control was withdrawn because it introduced a regression. After upgrading to this version, the commit and get latest tabs could display the error "System.FormatException: The string was not recognized as a valid DateTime. There is an unknown word starting at index 0."

5.3.3 - October 27th, 2016



  • "Link or unlink static data" and "Edit filter rules" are now split into two separate windows

5.3.2 - October 19th, 2016



  • SOC-8023: When applying data changes in the Get Latest tab, the message is now formatted correctly
  • SC-9065: Fixed a crash that could occur when comparing a SQL user to a Windows user
  • SC-9058: SQL Source Control now accepts the AT TIME ZONE syntax

5.3.1 - October 13th, 2016



  • The current branch name will be shown in the commit tab when a database is linked using git.


  • The 'Add migration script' button on the commit notification no longer disappears when the SQL Source Control window is made small.

  • Fixed a typo in the splash screen that appears when SQL Source Control is unlicensed.

  • SOC-8227, SC-8933, SC-7963, SC-9031: Errors or inconsistencies detected during registration are no longer incorrectly reported with the message "a duplicate object name has been found". Instead, more helpful descriptions of the errors are given.

  • SC-8716: Indexes on a column are not recreated when the only change to the column is the modification of a DEFAULT constraint

  • SC-8702: Users named after Windows principals are now equal even if their domains are different

  • SC-8409: Fixed a crash when failing to fetch encrypted object text

  • SC-9003: Correctly identify differences in stored procedures with comments between create statement and object name

  • SC-8965: Include existence checks for roles in the deployment script, when "Add object existence check" is specified.

  • SC-8989: Fixed filter checkboxes for projects loaded using the SSMS Integration Pack

  • SC-8939: Use fully qualified name of table types columns in table definitions

  • SC-8953: Projects loaded using the SSMS Integration Pack now load with the correct 'Nothing excluded' filter

  • SC-8948: When renaming a table and a column in the same deployment the correct existence check will now be written in the deployment script.

  • SDC-2193, SC-8964, SC-8973: SQL Compare now correctly ignores whitespace in comments when "ignore whitespace" option is used

5.3.0 - September 16th, 2016 

We’ve been updating how licensing works in the Redgate products. You’ll now be prompted to login with a Redgate ID to activate a newly installed product, or to upgrade an existing product to a new major or minor version. This unlocks better license management, and makes it easier to use Redgate software on multiple machines. Once a product is activated with a Redgate ID, we’ll be able to show you your licenses and some basic information about usage, and provide the ability for you to deactivate unused licenses. For now the license management functionality will only be available through the license management portal on the website. Down the line, we’re planning to offer some of these capabilities from within the software itself.


  • SOC-8196: Prevented an intermittent issue where SQL Source Control fails to load in SSMS.

Release notes for previous frequent update releases

Version 5.3.0 rolls up all of the changes from frequent update versions 5.1.1 to 5.2.4 - if you want to receive these kinds of updates more quickly in future, you should turn on Frequent Updates


Didn't find what you were looking for?