1.16.18107 - April 17th, 2018

Fixes

• Fix error during build and when attempting to generate a migration: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms

Improvements

• Update bundled OctoPack from version 3.6.1 to 3.6.3
• Update SQL Compare Engine to ver. 13.3.2.4090

1.16.18100 - April 10th, 2018

Fixes

• Fixed an issue where the final character of a batch ending in a temporal table statement might be cut off during package script generation
• Fixed an issue where ReadyRoll would display an error dialog when loading a project
• OctoPack no longer logs warnings at build time when packaging a sqlproj file for deployment with Octopus (Note: MSBuild 15.0 or Visual Studio 2017 is required). If you want OctoPack to keep logging such warnings anyway, add the following argument within your Continuous Integration build configuration: /p:MSBuildWarningsAsMessages=[blank]

Improvements

• Create development and shadow databases automatically for local instances when a hostname is used and no pre-deployment script is present
• Fix issue with incorrect error displaying when trying to build against a database that cannot be connected to
• Improve error handling in MSBuild tasks, in particular give more information for a cryptic "One or more errors occurred" message
• Add logging to a file for MSBuild tasks; the log file can be found in %localappdata%\Red Gate\Logs\ReadyRoll\MsBuild\ReadyRoll-MsBuild.log

1.16.18088 - March 29th, 2018

Fixes

• Fix bug causing high CPU utilization when the RedgateClient Windows service is stopped
• Fix bug causing failures performing command line build actions under .Net 4.6
• Display script verification failure details instead of a catch-all error dialog on 'Import and Generate Script' when erroneous migrations have been deployed
• Fix bug causing Refresh to fail when only the ShadowServer property is set in the sqlproj file
• Fix bug where empty SQL Server Authentication passwords would cause ReadyRoll to hang
• Fix bug where hidden objects are imported
• Fix incorrect message in patch build output where programmable objects were reported as "marked as deployed" instead of "deployed"

Improvements

• Update SQL Compare Engine to ver. 13.2.5.3979
• A more informative message appears during report generation when a schema snapshot cannot be found in the target database
• Added pre and post script information to patch build output

Changes

• When generating a migration script, filtered objects are now filtered when dependent on unfiltered objects
• In Octopus Deploy, deployment warnings are no longer raised when the database package does not contain a schema snapshot file
• When the shadow database exists but the MigrationLog table doesn't, we now no longer drop and recreate it

1.16.18080 - March 21th, 2018

Fixes

• Fix regression where opening a project that has the AlwaysUseDefaultConnectionForShadowDatabase property set to a value that can't be converted to a boolean resulted in an exception

1.16.18079 - March 20th, 2018

Fixes

• Fix incremental sqlproj builds when only the patch deployment script is output (i.e. the SQLCMD package (.sql) project option is unchecked)
• Fix an issue with pre and post deployment scripts not being included at project creation

1.16.18078 - March 19th, 2018

Fixes

• Fix regression where performing a build that generates a patch script, marking as deployed, and generating a drift correction script would all fail with an Azure SQL Database

1.16.18074 - March 15th, 2018

Fixes

• The baseline script generated by the Getting Started wizard now includes all SQL Server 2012+ language features supported by the SQL Compare engine, such as sequences, temporal tables and security policies
• Fix regression where "Programmable Objects => Import into separate script files" option is ignored (introduced in 1.16.18052)

Improvements

• Upgrade SCE/SDCE from 13.2.0.3596 to 13.2.2.383

Changes

• For ReadyRoll Pro customers: Programmable Objects are now enabled by default in newly-created projects (previously, the default setting resulted in stored procedures, functions and views being imported into Migrations). Note that any projects created before this release will preserve their existing Programmable Objects setting.
• The option to SuppressConnectionWarnings when a shadow database is not provided during build is no longer supported.

1.16.18059 - February 28th, 2018

Fixes

• Enabling the Programmable Objects feature is now possible when the database contains natively-compiled objects or table-valued functions associated with security policy objects (these scripts are placed in the Unsupported folder)

Improvements

• If verification fails due to a memory-optimized table dependency error, the tool-window will now provide guidance on how to add the missing filegroup to the project
• Integration of Redgate bulk uninstaller

Changes

• New strategy of generating package deployment scripts (WrapInExecuteWithSingleSetNoExec) enabled by default for all projects, which may result in faster deployments. The old strategy (WrapInExecuteConditionally) is going to be retired in a future release, so if you encounter any issues when using the new one, please let us know.

1.16.18052 - February 21st, 2018

Fixes

• Upgrade SCE/SDCE from 13.1.11.3480 to 13.2.0.3596
• Upgrade RGC from 4.0.4 to 4.0.8
• Builds now work again when pre or post scripts are readonly

Improvements

• Do not write USE T-SQL statements between post deployment scripts when patch scripts are generated for databases on Azure.

Changes

• Always store the relative path of Migrations and Programmable Objects in the script_filename column of the __MigrationLog table (previously only the name was stored if Semantic Versioning was disabled)

1.16.18038 - February 7th, 2018

Fixes

• Fixed a bug where certain special characters (such as double quotes; '"') in SQL Auth passwords would not work with SQLCMD when deploying in Visual Studio or via MSBuild
• Fixed an issue with multi-project solutions where the wrong project was shown in the project dropdown
• Fixed an issue with partial-project solutions whereby scripts from dependency projects were excluded from build-time verification (i.e. not included in Shadow Database deployment)
• Fixed an issue with the deployment preview and drift reports in partial-project solutions whereby modifications to existing objects would erroneously appear as "Added"

Improvements

• Improved load time for larger solutions by limiting the number of individual migrations displayed on the Messages tab of the Error List to 20 (per project)
• Set flag "Always use default connection string for Shadow Database" automatically as part of the initial baselining wizard if Development Database is hosted on Azure
• Perform drift analysis during build when Shadow Database isn't specified
• Allow creation of non-ReadyRoll projects using the "Create project..." button in the ReadyRoll window
• Add the date to ReadyRoll-VS.log in ISO 8601 format
• Upgrade SQL Compare Engine to 13.1.11.3480

1.16.18018 - January 18th, 2018

Important information

After upgrading to this release, you may notice that the Deployment Preview and Drift Reports do not generate, and the following warning is output in the build log:

No snapshot could be retrieved from the target database; no report will be generated until your next deployment.

This occurs due a change in the way that ReadyRoll generates these reports. To resolve, perform a deployment of your database to the target server using the artifacts from the relevant build (this inserts a schema snapshot into the target server/database). When you next perform a build against the target server/database, the reports should start generating again.

Fixes

• Fix the rendering of the names of dependencies in the .exe installer

Improvements

• New and improved getting started wizard
• Upgrade SQL Compare Engine to 13.1.9.3372

Changes

• Remove legacy method of report generation - no reports will be generated on first deployment to a database