Skip to end of metadata
Go to start of metadata

3.0.19128.7440 - May 8th, 2019

Improvements

  • Updated SQL Compare Engine to 13.7.13.10598

3.0.19120 - April 30th, 2019

Fixes

  • Fixed a bug where the DeployPath variable would be set incorrectly when deploying via MsBuild

Improvements

  • Updated SQL Compare Engine to 13.7.11.10438

3.0.19115 - April 25th, 2019

Fixes

  • SCA-2582: Fixed a problem where some deployment scripts would not be run against the deployment target when USE statements were present in the previous scripts.
  • SCA-2583: The baselining strategy property will be correctly set after baselining a project

Improvements

  • Updated SQL Compare Engine to 13.7.11.10396

3.0.19106 - April 16th, 2019

Fixes

  • SCA-2595: Fixed a bug where conditions for a migration were not being respected on the package script.

Improvements

  • Updated SQL Compare Engine to 13.7.10.10286

3.0.19099 - April 9th, 2019

Improvements

  • Updated SQL Compare Engine to 13.7.9.10193

3.0.19092 - April 2nd, 2019

Improvements

  • Updated SQL Compare Engine to 13.7.9.10117

3.0.19085 - March 26th, 2019

Improvements

  • Updated SQL Compare Engine to 13.7.7.10009

3.0.19080 - March 21st, 2019

Changes

  • MSBuild 4.0 is no longer supported. MSBuild 15.0 can be downloaded from https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=15.

Improvements

  • Updated SQL Compare Engine to 13.7.7.9955

3.0.19073 - March 14th, 2019

Fix

  • Visual Studio 2019 version number fix

3.0.19073 - March 14th, 2019

Features

  • Support for Visual Studio 2019

Fixes

  • SCA-2556: Fixed an issue where scripts for aggregates were not idempotent

3.0.19072 - March 13th, 2019

Fixes

  • SCA-2555: Fixed an issue that caused project loading to fail

3.0.19066 - March 7th, 2019

Fixes

  • SCA-2549: Fix an issue where objects with no differences appear on refresh
  • Fixed an issue locating SqlCmd executable for SQL Server 2008
  • Fixed an issue creating a database or deploying to a database after opening an existing project with no database specified

Improvements

  • Updated SQL Compare Engine to 13.7.5.9770

3.0.19059 - February 28th, 2019

Improvements

  • Made patch deployment scripts more consistent between Azure and non-Azure existing target databases

3.0.19052 - February 21st, 2019

Fixes

  • SCA-2548 : Fixed a bug in regular expression parsing for filter settings
  • SCA-2547 : Fixed a bug causing an error 'Could not load file or assembly 'System.ValueTuple..." when using import and generate scripts
  • Fixed an issue where SQL parsing errors were not all being displayed

Improvements

  • Updated SQL Compare Engine to 13.7.3.9474

3.0.19043 - February 12th, 2019

Features

  • Updates SQL Compare and SQL Data Compare to 13.7.2.9296

Fixes

  • SCA-2543: SQL Change Automation no longer fails to generate programmable objects where there is a case-sensitivity discrepancy when SyncOptionCaseSensitiveObjectDefinition is false
  • SCA-2544: SQL Change Automation no longer incorrectly displays a "SQL Change Automation encountered an error" message when certain errors occur in other Visual Studio components
  • SCA-2545: Fixed an issue where disabling static data for tables with pending data changes might cause an error on refresh
  • Fix an issue where a dialog box about unsupported objects could cause crashes

3.0.19028 - January 28th, 2019

Fixes

  • SQL Change Automation can now create a shadow database for usernames containing apostrophes
  • SCA-2542: Fixed regression that caused a System.Xml.XmlException while generating diff and drift reports

Improvements

  • Updated SQL Compare Engine to 13.6.12.8993

3.0.18341 - December 7th, 2018

Improvements

  • Output data used to generate a deploy preview HTML report to a separate file in a JSON format
  • Updated SQL Compare Engine to 13.6.6.8354
  • Start supporting builds from Visual Studio when solution folder includes a URL encoded space (%20) in the path

3.0.18331 - November 22nd, 2018

Fixes

  • Fix regression of missing netstandard dll
  • Fixed a regression that caused the 'Cannot modify an evaluated object originating in an imported file' error message to appear. This is related to removing obsolete settings from the project file.

3.0.18326 - November 22nd, 2018

Fixes

  • Fixed a possible regression where changes to the Programmable Objects and Offline Schema Model folders would not be added to the project

Improvements

  • Updated SQL Compare Engine to 13.6.5.8246

3.0.18324 - November 20th, 2018

Fixes

  • Fixed an issue where running SQL Change Automation and SQL Prompt concurrently with mismatched versions could cause errors
  • Fixed an issue where builds would fail requesting a baseline when multiple projects were using the same development database
  • Fixed an issue where we would incorrectly detect SqlCmd as failing to have run correctly
  • Fixed baselining when targetting an empty database during initial project setup
  • SQL Server version is now set during initial setup when no target database is set

Improvements

  • Updated SQL Compare Engine to 13.6.4.8177
  • Added line numbers to generated html report
  • Updated VCS integration to only try and checkout modified files from source control on programmable object and offline schema model update
  • The obsolete GenerateCreateScript option will be removed from .sqlproj files - this previously controlled the creation of .dacpac packages which were deprecated in February 2017
  • Removed ExcludeObjectsFromSync property in favour of in-memory persistence of user's choices of exclusions during refresh. As a result objects unchecked before import will not still be unchecked if a project is closed and then reopened. Persistent filtering should be achieved using Filters.

3.0.18291 - October 18th, 2018

Fixes

  • SCA-75: Objects created WITH ENCRYPTION no longer cause SQL Change Automation to fail during refresh with the error "Cannot load the Backup Reader dll"
  • SC-10234: TRIM functions are now correctly imported
  • SC-10253, SC-10255, SC-10272: Improved refresh performance when the Ignore NOT FOR REPLICATION option is enabled
  • SCA-70, SC-10264: User defined types are no longer incorrectly imported as Programmable Objects

Improvements

  • Support database objects with an apostrophe in names
  • Fix condition of User-defined Data Types existence in the Offline Schema Model folder from OBJECT_ID to TYPE_ID
  • Updated the SQL Compare Engine to version 13.6.1.7928

3.0.18283 - October 10th, 2018

Fixes

  • Fix regression of missing sqlite3.dll
  • Fix regression when RedGateDatabaseInfo.xml file cannot be overriden

3.0.18282 - October 9th, 2018

Improvements

  • Extend logging from Visual Studio. The log files are stored in %localappdata%\Red Gate\Logs\SQL Change Automation\.

3.0.18275 - October 2nd, 2018

Fixes

  • Fix the issue on the "Script verification failed" view when sometimes the output from SQL Server was not presented.
  • Fix an exception on the "Script verification failed" view when navigating to a specific line of a script was impossible.
  • Project properties page doesn't have duplicated sections anymore when it is opened from the top menu

Changes

  • DeployPath is now never set in patch scripts, and is instead set on deployment. If you use $(DeployPath) variable in your patch script and want to execute it manually, you need to add it to the script yourself or pass it to sqlcmd.exe.

3.0.18262 - September 19th, 2018

Improvements

  • Updated the SQL Compare Engine from version 13.4.4.6824 to version 13.5.0.7579

Changes

  • DeployPath may no longer be explicitly set in patch scripts, and is instead always provided on deployment

3.0.18249 - September 6th, 2018

Fixes

  • Fix a bug where the SQL Change Automation package load can fail in VS 15.8 if the SQL Change Automation pane wasn't visible before opening a project
  • Fix a bug where a user could become stuck on the progress screen after an error reverting a change
  • Single quotes in conditions for migration scripts/programmable objects are now correctly escaped when they are used in PRINT statements

Improvements

  • Remove Delete Script button from notification bar after an imported migration script has been verified
  • Modified the Publish dialog and Output Types section in project properties to include links to the docs page Deploying SQL Change Automation Projects
  • Sort database object names stored in the ExcludeObjectsFromSync property

Changes

  • SQL Server Management Studio 2008 is no longer supported for the Open in SSMS tool-window command within the Visual Studio extension. Note that later versions of SSMS continue to be supported.

3.0.18200 - July 19th, 2018

Fixes

  • Fix SqlCmd error The certificate chain was issued by an authority that is not trusted when attempting to deploy to an on-premises SQL Server instance using Active Directory authentication
  • Fix regression when the Script Status Margin is not visible in a SQL file editor if SQL Change Automation window wasn't opened before

Improvements

  • Handle verification errors more gracefully
  • Updated the SQL Compare Engine from version 13.4.3.6725 to version 13.4.4.6824

Changes

  • Removed support for the project setting value WrapInExecuteConditionally for PackageScriptBatchExecutionStrategy. The value WrapInExecuteWithSingleSetNoExec is now the default and only value supported. Please note that the corresponding project property will be removed from the .sqlproj if this setting has been set to a value other than WrapInExecuteWithSingleSetNoExec for the project. This can be safely removed manually if the build environment is up to date.
  • In the project properties, remove UI for producing a SQLCMD package on build. Also remove UI for producing a Octopus Deploy package on build, and generating Octopus NuSpec file to be included in the project.
    • These options are still supported, only they can no longer be set using the UI and must be manually edited in the .sqlproj file. See this documentation page for more information.

3.0.18190 - July 9th, 2018

Fixes

  • Updated the SQL Compare Engine from version 13.3.4.6105 to version 13.4.3.6725
  • Fix bug where the new project wizard allows you to set an invalid development database.

Improvements

  • Enforce minimum SQL Change Automation version to be used if migration grouping is set to 'Order by file path'.
  • Handle configuration errors more gracefully

Changes

  • The Target platform for newly-created projects is now set to SQL Server 2016 by default (was SQL Server 2012). Please note that any existing projects will retain their current DSP setting.

3.0.18177 - June 26th, 2018

Fixes

  • Fix an issue where certain types of scripts (programmable objects, pre- and post-scripts) that have lines separated by a carriage return character only (without a line feed) would fail to deploy
  • Fix Azure SQL Database does not support switching between databases error when attempting to deploy a package to an Azure SQL database with SQL Server set as the target platform
  • Fix a bug with initial baseline process when development database set to <default> on a non-local SQL Server instance in the setup wizard
  • Fix a regression when Deploy Project button doesn't work for projects that reference ReadyRoll.MSBuild NuGet package in version lower than 3.0

Improvements

  • A warning is now raised during package-based deployment if there is a mismatch between the platform type and the platform of the specified database server
  • Prevent Visual Studio from terminating in the scenario where a change to a project setting is made when the project is read-only (or the user does not have permissions to edit the file) and the modification is subsequently cancelled by the user

Changes

  • Deployment behavior change: When the database already exists, and the project is deployed via PowerShell/VSTS/Octopus using the package 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 behavior, add a USE [master] statement to the top of your Pre-Deployment 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 consistency with deployments performed within Visual Studio, and to lay groundwork for future improvements to Azure SQL Database support.
  • Generated migration scripts no longer disable and re-enable DDL Triggers

3.0.18169 - June 18th, 2018

General

ReadyRoll has been renamed to SQL Change Automation, and merged with the functionality previously provided by DLM Automation.

Features

  • Reports have moved from build time to release time, so that a report can be generated and reviewed before deployment to every environment
  • Builds can now utilise SQL Doc to produce database documentation
  • tSQLt tests run during build can now utilise SQL Data Generator to create realistic test data

Changes

  • Create new migrations with UTF8-with-BOM encoding, so special characters in manually-added migration are preserved in a deployment script
  • No labels