SQL Change Automation SSMS 4.1 release notes
Published 11 November 2019
4.1.20014 - January 14th, 2020
Improvements:
- Updated SQL Compare Engine to 14.1.9.14577
Features:
- Added the ability to set shadow database in the UI after creating a new SQL Change Automation project using SQL Source Control as a development source.
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
Fixes:
- SCA-2656 - Apply action no longer executes baseline scripts against a populated development database
- SCA-2653 - The default Filter.scpf filter file now gets picked up immediately if added to the project root, if no custom filter file is specified
- SCA-2667 - The baseline script now includes partition schemas and functions when the
SyncOptionIgnoreDataspaces
is turned off - SCA-2655 - The generate migrations page is now responsive when there are large amounts of changes
- Refresh no longer fails with an error if a baseline script is generated and then deleted - this validation will still produce an error on verify
4.1.19350 - December 16th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.6.14212
Features:
- Added the ability to create a new SQL Change Automation project using SQL Source Control as a development source.
- Added support for
NoAutoColumnMapping
SQLCompare option viaSyncOptionNoAutoColumnMapping
setting
4.1.19344 - December 11th, 2019
Improvements:
- Creating a new database is no longer an option when setting up a baseline
- Updated SQL Compare Engine to 14.1.6.14149
Features:
- Added the ability to update the development source to a SQL Source Control project.
4.1.19336 - December 3rd, 2019
Features:
- Added the ability to specify which columns in static data tables should be tracked.
Improvements:
- Updated SQL Compare Engine to 14.1.5.14025
Fixes:
- Fixed a performance issue on the static data page when repeatedly opening and closing the add tables panel.
4.1.19330 - November 26th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.5.13997
- Redesigned connection dialog
- The default operation timeout is now increased to 5 minutes. This will not affect existing installations. This timeout can be manually configured.
- SCA-84: New projects now support SQL Server 2019 syntax by default, such as
ADD SENSITIVITY CLASSIFICATION
4.1.19324 - November 20th, 2019
Improvements:
- Updated SQL Compare Engine to 14.1.4.13897
- Added support for SQL Compare option
OnlineIndexBuild
Fixes:
- Fix for some circumstances where the out of process component of SQL Change Automation in SSMS could not be communicated with without running SSMS as an administrator due to permissions with certificates.
- The out of process component of SQL Change Automation will now attempt to re-create its certificate if it could not be read.
4.1.19317 - November 13th, 2019
Features:
- Added the ability to use a SQL Source Control project as a development source. SQL Change Automation will compare the contents of your SQL Change Automation project against the SQL Source Control project in order to generate new migration scripts.
Improvements:
- Updated SQL Compare Engine to 14.1.3.13803
- Added support for SQL Compare option
IgnoreDynamicDataMasking
via configurationSyncOptionIgnoreDynamicDataMasking
in project file
Fixes:
- SCA-2654: You can now generate migrations with over 1000 changes and baseline from databases with more than 1000 programmable objects
4.1.19315 - November 11th, 2019
Features:
- SQL Change Automation in SSMS now supports configuring and generating migrations for static data
Improvements:
- The operation timeout value can now be configured
- Updated SQL Compare Engine to 14.1.1.13668
- Improved error handling on the verify page