SQL Source Control 5.6 release notes
Published 02 May 2017
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.6.1 - May 10th, 2017
Fixes
- SOC-4684: The 'unselect all' button no longer fails to deselect items when there is a conflict in the list of objects to commit or get
- SOC-8800: SQL Source Control no longer prevents Object Explorer expanding database nodes for SQL Server 2000 databases in SQL Server Management Studio 2012 and above
- SOC-8801: SQL Source Control no longer fails to install on systems that only have SQL Server Management Studio 17 installed
- SOC-8804: Commit warning messages are no longer shown for objects that have been filtered out of the commit list
- SOC-8805: The Git current branch name now updates correctly when the list of changes is refreshed (by changing tabs or clicking the refresh button)
Version 5.6.1 rolls up the changes from frequent update version 5.6.0 - if you want to receive these kinds of updates more quickly in future, you should turn on Frequent Updates
5.6.0 - May 2nd, 2017
FREQUENT UPDATES RELEASE
Fixes
- SOC-5919: SQL Source Control no longer occasionally fails with the message 'failed to update file from source control' while trying to determine changes.
