SQL Change Automation 4

SQL Change Automation Visual Studio 4.3 release notes

4.3.20336 - December 1st, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.14.17499

4.3.20330 - November 25th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.12.17429

4.3.20324 - November 19th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.12.17385

Fixes:

  • SCA-2773 - Fixed build for projects using SQL Clone
  • SCA-2774 - The default provisioning script now encloses the database name in square brackets, to prevent incorrect syntax errors

4.3.20316 - November 11th, 2020

Improvements:

  • SCA-2761 - Reduced the comment length when generating offline schema model files

4.3.20309 - November 4th, 2020

Improvements:

  • SCA-2762 - The default CreateDatabase.sql script, used to provision development or shadow databases, will now create Azure DB as BASIC edition by default for new projects. This file can be customised to tweak this behaviour.
  • Updated SQL Compare Engine to 14.4.10.17208

4.3.20295 - October 21st, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.9.17023

4.3.20288 - October 15th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.7.16960

4.3.20280 - October 6th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.7.16917

Fixes:

  • SCA-2764 - Shadow now correctly rebuilds when there are applied migrations in the shadow database, and no migrations on disk.

4.3.20272 - September 28th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.5.16843

Fixes:

  • SCA-2756 - Fixed misleading build warning when programmable scripts objects exist but ProgrammableObjectHandling is set to ScriptInMigrations

4.3.20267 - September 23rd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.3.16779

Fixes:

  • SCA-2729 - Fixed an issue where the list of pending migrations did not show correctly

4.3.20259 - September 15th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.3.16730

4.3.20252 - September 8th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.2.16694

4.3.20246 - September 2nd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.4.2.16668

4.3.20238 - August 25th, 2020

Improvements:

  • Added comment to offline schema model scripts to help explain how to use them

4.3.20233 - August 20th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.3.5.16614
  • Added the option to set the log level using the help drop-down menu in SQL Change Automation.

4.3.20224 - August 11th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.3.4.16560

4.3.20211 - July 29th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.3.2.16499

Fixes:

  • Fixed an issue where a missing Newtonsoft.Json dll might occur in Visual Studio 2017 and Visual Studio 2015.

4.3.20209 - July 27th, 2020

Improvements:

  • Updated SQL Compare Engine to 14.3.1.164

Fixes:

  • Fixed an issue where a missing Newtonsoft.Json dll might occur after an update.

4.3.20205 - July 23rd, 2020

Improvements:

  • Updated SQL Compare Engine to 14.3.1.16483

Features:

  • Added new project setting ProgrammableObjectHandling which replaces existing setting DeployChangesForProgrammableObjects Any existing projects which contain DeployChangesForProgrammableObjects will have the new setting added. The old setting will not be removed automatically as that might break continuous integration pipelines using older versions of the product. The new setting has three values:
  • ScriptInMigrations - Equivalent to previous false behaviour. i.e. no programmable objects
  • UseRepeatableScriptsForAllObjects - Equivalent to previous true behaviour. i.e. all programmable objects scripted out at baseline and thereafter
  • UseRepeatableScriptsForModifiedObjects - Programmable objects are scripted out in the offline schema model during baseline, but to the programmable objects folder thereafter. When an object is scripted to the programmable objects folder, it is removed from the offline schema model folder.
  • The offline schema model will now be scripted out after running through the baselining wizard, if no target database is selected for baseline but a provisioner is configured.
  • The development database can now be created using the configured provisioner
  • It is now possible to create down scripts alongside migration scripts by creating files prefixed with U_
  • It is no longer necessary to specify the SkipBaselineCheck property when a provisioner is configured

Changes:

  • Logging library has been changed to match SQL Change Automation in SSMS.

Fixes:

  • Improved project load behaviour when development database does not exist and the baseline wizard hasn't been run
  • Improved connection validation in baseline wizard when default database is selected
  • Improved error handling when duplicate sql cmd variables are defined
  • Fixed stack traces which might appear in logs on project load
  • Fixed error when cancelling mark as deployed

Didn't find what you were looking for?