SQL Change Automation Visual Studio 4.1 release notes
Published 11 November 2019
4.1.20014 - January 14th, 2020
Improvements:
- Updated SQL Compare Engine to 14.1.9.14577
4.1.20006 - January 6th, 2020
Improvements:
- SCA-2674 - We now raise an error during build for unnamed primary key constraints in addition to existing unnamed constraint scenarios to produce deterministic comparison behavior. Note that this may cause scripts which previously passed build validation to start failing. Fix this by using e.g.
ID INT NOT NULL, CONSTRAINT [MY_PK] PRIMARY KEY ([ID])
in place ofID INT NOT NULL PRIMARY KEY
. - Updated SQL Compare Engine to 14.1.8.14375
- SCA-2638 - We no longer generate a migration script when the SSDT
Generate Script
button is clicked when designing SQL objects in Visual Studio. This behaviour has never been supported in Visual Studio 2019. We recommend updating the database and using the SQL Change AutomationImport and generate scripts
button, which will take into account the configured comparison options. - SCA-2638 - We no longer write an EntityFramework code-first migration scripts to the migration scripts folder when the Package Manager command is run within Visual Studio. This behaviour was always branded as experimental and has never been supported in Visual Studio 2019. We recommend creating SQL Change Automation scripts manually and copying the entity framework code inside (either setting the TransactionHandling attribute to Custom or manually removing the generated transaction handling code) or generating migrations directly through SQL Change Automation.
Fixes:
- SCA-2609 - Prevent being able to click the import and generate script button multiple times and show a progress screen while the import is in progress.
- SCA-2618 - Do not prompt to finish setting up project on loading or reloading project if the user opted out when running the setup wizard. It is still possible to return to this screen by manually switching baselining on in the project settings and reloading the project.
- Remove
Backup Shadow database when a drop/create is required
andSkip Shadow backup when working with a local instance of SQL Server
legacy options. - SCA-2667 - The baseline script now includes partition schemas and functions when the SyncOptionIgnoreDataspaces is turned off
- SCA-2675 - Migration generation result now displayed instead of blank screen
- SCA-2662 - Addressed errors when pressing import immediately following deletion or pressing import multiple times
- Refresh no longer fails with an error if a baseline script is generated and then deleted - this validation will still produce an error on build
4.1.19350 - December 16th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.6.14245
Features:
- Added support for
NoAutoColumnMapping
SQLCompare option viaSyncOptionNoAutoColumnMapping
setting
4.1.19344 - December 11th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.6.14149
4.1.19336 - December 3rd, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.5.14025
4.1.19330 - November 26th, 2019
Improvements:
Updated SQL Compare Engine to 14.1.5.13997
SCA-84: New projects now support SQL Server 2019 syntax by default, such as
ADD SENSITIVITY CLASSIFICATION
Fixes:
- SCA-2670 - Fixed an issue where deploying solutions with multiple projects was failing
4.1.19324 - November 20th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.4.13897
- Added support for SQL Compare option
OnlineIndexBuild
4.1.19317 - November 13th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.3.13803
- Added support for SQL Compare option
IgnoreDynamicDataMasking
via configurationSyncOptionIgnoreDynamicDataMasking
in project file
4.1.19315 - November 11th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.1.13668