SQL Change Automation 4

SQL Change Automation Visual Studio 4.2 release notes

4.2.20176 - June 24th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.18.16218

Fixes:

  • SCA-2726 - Fixed potential error when opening a project without a user file
  • SCA-2728 - Ensured that we display the connection failed screen instead of the unhandled error screen for database connection failures with Azure Active Directory authentication types
  • SCA-2731 - Fixed potential issue when deleting objects containing ''
  • SCA-2732 - Fixed issue where DeployPath variable was set incorrectly when performing deploy through Visual Studio

4.2.20168 - June 16th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.17.16086

4.2.20161 - June 9th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.17.16043

4.2.20154 - June 2nd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.16.15991

Changes:

  • Failure to drop shadow database during Clean operation now treated as an error

4.2.20147 - May 26th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.15.15905

4.2.20143 - May 22nd, 2020

Fixes:

  • Fixed incorrect collation in default CreateDatabase.sql file for new projects

4.2.20140 - May 19th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.15.15842

4.2.20133 - May 12th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.14.15791

Features:

  • New projects now use the custom provisioning scripts feature by default. Logic for creating a database is now located in a CreateDatabase.sql script inside the Provisioning folder, instead of in a placeholder pre-script. This allows the shadow database to be located on an Azure instance. Note that it is still generally recommended to locate the shadow database locally where possible as that will usually result in a faster database connection. The default CreateDatabase.sql and DropDatabase.sql scripts can be altered to improve performance or implement custom provisioning logic.

4.2.20126 - May 5th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.13.15750

4.2.20120 - April 29th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.11.15654

Fixes:

  • SC-10818: Fixes issue generating programmable objects and offline schema model when database contains triggers referencing system tables

4.2.20118 - April 27th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.11.15576

Features:

  • Added 'UseCreateOrAlterForRerunnableScripts' option for using CREATE OR ALTER for programmable objects (experimental)

Changes:

  • BaselineUpToMigrationId property is no longer supported
  • Deprecated ordering of migrations by file name. This will now produce a warning on build. Please switch to ordering by file path by setting the MigrationOrdering property to FilePath. This will behave identically if you have no subfolders within the Migrations folder. If this poses a problem please contact RedGate support.
  • Deprecated the DeploymentMode property. This will now produce a warning on build.
  • Deprecated integration with Octopus Deploy via MsBuild. This will now produce a warning on build. We recommend updating to use the PowerShell cmdlets and the associated Octopus Deploy step templates. If this poses a problem please contact RedGate support.

4.2.20112 - April 21st, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.10.15551

4.2.20106 - April 15th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.9.15498

Changes:

  • AfterDatabaseSync custom MsBuild target is no longer supported

4.2.20098 - April 7th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.9.15488

4.2.20094 - April 3rd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.8.15461

Changes:

  • ExcludeObjectsFromImport property is no longer supported. Please use Filter.scpf file instead.
  • BuildOptionBackupShadowDatabase property is no longer supported.

4.2.20091 - March 31st, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.8.15435

Features:

  • If you specify an explicit shadow database connection string with no initial catalog, the shadow database name will continue to be derived from the development database, and respond to development database changes

4.2.20085 - March 25th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.6.15402

Fixes:

  • SCA-2693 - Fixed an error with incremental builds of baselined projects in SCA VS

4.2.20078 - March 18th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.6.15379

Fixes:

  • SCA-2701 - Fixed Connection dialog glitches with Azure Active Directory Password authentication

4.2.20066 - March 6th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.4.15307

4.2.20064 - March 4th, 2020

Fixes:

  • SCA-2701 - Fixed errors during refresh with Azure Active Directory Password authentication

4.2.20058 - February 27th, 2020

Improvements:

  • Additional diagnostic logging for build process

Fixes:

SCA-2697 - We no longer sometimes swallow useful error messages during the build process

4.2.20057 - February 26th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.3.15157

4.2.20056 - February 25th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.3.15157

4.2.20050 - February 19th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.2.15114

4.2.20042 - February 11th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.1.15027

4.2.20036 - February 5th, 2020

Fixes:

  • SCA-2672 - Improved logic for selecting the most recent sqlcmd version

4.2.20030 - January 30th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.2.1.14869

Fixes:

  • SCA-2684 - We now return a consistent error if multiple operations try and access the development or shadow database while a write operation is already in progress

4.2.20023 - January 23rd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.1.10.14743

4.2.20022 - January 22nd, 2020

Fixes:

  • SCA-2685 - We no longer remove braces from the Visual Studio project guid

Didn't find what you were looking for?