ReadyRoll 1.17 release notes
Published 24 May 2018
100.0.18169 - June 18th, 2018
On Monday 18th June 2018, we released a major upgrade to ReadyRoll. As part of that major upgrade we renamed ReadyRoll to SQL Change Automation.
This release of ReadyRoll is for users without a support and upgrades package, who aren't entitled to upgrade to SQL Change Automation. This release won't be auto-upgraded to SQL Change Automation by Visual Studio.
1.17.18158 - June 7th, 2018
- Fixed an issue where SemanticVersioning wasn't being honoured when using 1.16 and 1.17 together.
1.17.18155 - June 4th, 2018
- Decrease Visual Studio start-up time by loading ReadyRoll in background
- Improve solution load time by populating the Error List in background
1.17.18150 - May 30th, 2018
- Fixed Visual Studio hang on solution load when ReadyRoll pane is open but hidden
- Fixed a regression when baselining a non-existent development database: Unable to retrieve a value for Server Properties from MYMACHINE\InstanceName
- Fixed an issue where migration scripts containing carriage return newlines would fail to deploy
1.17.18144 - May 24th, 2018
- Fixed naming of new empty migrations in sub-folders when Semantic Versioning is disabled
- The database extended property
IsSQLCloneDatabaseis now ignored in ReadyRoll for better integration with SQL Clone and SQL Provision
- Fixed an issue where script generation might mark baseline scrips as deployed instead of executing them, following a previous error in a script with custom transaction handling
- Fixed issue where project properties could not be opened with invalid semantic versioning or baselining configuration
- It is now possible to order migrations by file path. The project properties UI has been updated accordingly.
- Update SQL Compare Engine to version 220.127.116.1105
- Improved contained database support by allowing deployments to be performed with users that only exist at the database level
- Improved logging of unhandled exceptions in VS
- Improved performance by reducing the number of database calls
- Reduced likelihood of deadlocks and multithreading related problems
- Deployment behavior change: When the database already exists, and the project is deployed within Visual Studio or via MSBuild using the patch method, the Pre-Deployment scripts will now be executed in the context of the target database, rather than the default database (typically
[master]). To retain the previous behaviour, add a
USE [master]statement to the top of your Pre-Deploymet script. Note that the db context in which migrations are executed in is unchanged; they will continue to execute within the context of the target db per current behavior. This change has been made to improve support for contained databases, and to lay groundwork for future improvements to Azure SQL Database support.
- Remove a mention of
ExcludeObjectsFromImportbecause it was deprecated in 1.15.17340 when we released filter rules to replace it.
- Changed a commented out MSBuild property in the project template to reflect that DML Triggers cannot be handled as a Programmable Object.
- Changed a commented out MSBuild property in the project template to use the new names for object types.
- Changed a build message to make it easier to copy/paste.