1.2.12.234 - November 25th, 2015

Feature

• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.4.0 release notes. 

1.2.11.209 - November 19th, 2015

Features

• Additional database connection string properties
  When using a database connection string in place of the New-DatabaseConnection cmdlet, you can now specify a number of additional properties. For more information see New-DlmDatabaseConnection Cmdlet reference.
• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.9 release notes. 

1.2.10.194 - November 11th, 2015

Feature

• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.8 release notes. 

1.2.9.123 - October 28th, 2015

Feature

• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.6 release notes. 

1.2.8.111 - October 21st, 2015

Feature

• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.5 release notes. 

1.2.7.104 - October 7th, 2015

Features

• Simplified activation
  We've simplified the way you activate SQL Release. You can now use the DLM Automation Suite app to activate SQL Release and all the other tools in the suite. For more information, see Activating.
• Choose how SQL Release determines compatibility level
  By default SQL Release uses the database's compatibility level to detect supported features. If you prefer, you can now get SQL Release to use server information to determine the compatibility level. To do this, use the -SQLCompareOptions parameter in the New-DatabaseRelease cmdlet to exclude the SQL Compare default option UseCompatibilityLevel. See Using SQL Compare options in SQL Release.
• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.3 release notes. 

1.2.6.97 - September 30th, 2015

Features

• Improved performance
  We've improved the startup performance of the SQL Compare engine that powers SQL Release, allowing it to deploy databases more quickly.
• New version of SQL Compare engine
  We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.3.2 release notes. 

1.2.6.91 - September 23rd, 2015

We've updated the SQL Compare engine that powers SQL Relase. For details of features and fixes, see the SQL Compare 11.3.1 release notes.

1.2.5.89 - September 17th, 2015 

Fix

• SQLREL-94: We've fixed a bug that was stopping the Changes.html report from opening in Chrome.

1.2.4.81 - September 16th, 2015 

We've updated the SQL Compare engine that powers SQL Relase. For details of features and fixes, see the SQL Compare 11.3.0 release notes.

Fix

SQLREL-92:

We've fixed the parsing error where SQL Release was failing to pick up static data in script folders when there was an opening parenthesis directly after the CREATE TABLE statement and on the same line.

However, if you edit the script, you still need to make sure the column definitions for the table are on subsequent lines.

Known issue

SQLREL-94:

The Changes.html report that's created as part of the database deployment resources currently won't open in Chrome. Open it in Internet Explorer or Firefox instead.

1.2.4.66 - September 2nd, 2015

Feature

• Simplified installation
  SQL Release is now installed as part of the DLM Automation Suite, so you no longer need to run a separate installation process.
  

Known issue

SQLREL-92:

We've had one report of SQL Release failing to pick up static data in the target database. You may have this problem if you see primary key violations, and a number of +INSERT statements in the static data section of the Changes.html file. 

We're working on a fix. In the meantime, the workaround is to open the creation script, look for the CREATE TABLE statement, and make sure there isn't an opening parenthesis directly after it on the same line. Scripts created using SQL Compare will not contain this formatting error. If you're editing the script, make sure the CREATE TABLE statement looks like this:

CREATE TABLE [dbo].[LookupAddressType]
(

and NOT like this:

CREATE TABLE [dbo].[LookupAddressType](

1.2.3.3168 - August 19th, 2015

We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.2.8 release notes. 

1.2.2.3142 - July 29th, 2015

We've updated the SQL Compare engine that powers SQL Release. For details of features and fixes, see the SQL Compare 11.2.6 release notes. 

1.2.2.3123 - July 22nd, 2015

We've added another new feature to the SQL Release step templates for Octopus Deploy.

Feature

Last week we added a TemporaryDatabaseServer parameter to the New-DatabaseRelease cmdlet. This week we've added a Temporary database server connection string parameter to the following step templates for Octopus Deploy:

• Redgate - Create Database Release
• Redgate - Deploy from Package

If you're using Migrations V2 beta, you can use the new parameter to specify the connection string of the SQL Server instance for a temporary database, instead of using LocalDB. This allows Migrations V2 beta to work with databases that have features not supported by LocalDB, such as Full-Text Search.

The latest versions of the step templates are available from the Octopus Deploy Library.
To learn more about installing and using the SQL Release step templates, see this worked example.

1.2.1.3109 - July 15th, 2015

This release contains a new feature in one of the SQL Release cmdlets for users of Migrations V2 beta.

Feature

We've added a TemporaryDatabaseServer parameter to the New-DatabaseRelease cmdlet. If you're using Migrations V2 beta, you can use this parameter to specify a SQL Server instance for the temporary database build instead of using LocalDB. This allows Migrations V2 beta to work with databases that have features not supported by LocalDB, such as Full-Text Search.

1.2.1.3062 - July 8th, 2015

In this release, we've updated the Redgate step templates for Octopus Deploy to include some new parameters added recently to the PowerShell cmdlets. 

Features

We've added two new parameters to the Redgate step templates for Octopus Deploy:

• Include identical objects in the change report: this parameter is supported in the Redgate - Create Database Release template. It overrides the default option to hide identical objects on the change report.
• Query batch timout: this parameter is supported in the following step templates:
  
  • Redgate - Deploy from Database
  • Redgate - Deploy from Database Release
  • Redgate - Deploy from Package
  The parameter lets you change the timeout duration for batches of queries in the update script. This is useful if one of the batches takes longer than the 30 second default timeout. To find out more, see Timeout expired error with Use-DatabaseRelease cmdlet.

The latest versions of these templates are available from the Octopus Deploy Library.

1.2.1.3032 - July 1st, 2015

This release contains a number of small fixes and improvements.

Feature

• The Export-DatabaseRelease cmdlet now supports the -Force parameter, allowing you to overwrite any previous export.

Fixes

• SQLREL-81: The New-DatabaseRelease cmdlet no longer ignores filter files within the db\states subfolders of the source path.
• SQLREL-87: In most circumstances, the Changes.html report no longer hangs when there are large number of difference lines.

1.2.1.2943 - June 24th, 2015

This release contains further improvements to the Changes.html report.

Features

We've made the Changes.html report easier to navigate and customize. You can now:

• navigate straight to the 'added', 'removed' and 'modified' sections
• expand and collapse the full SQL for each object
• include identical objects using a switch parameter in the the New-DatabaseRelease cmdlet. They're no longer included in the report by default.
  If you want to include them, see How do I include identicals in my change report?

1.2.1.2869 - June 17th, 2015

This release contains further improvements to the Changes.html report.

We've also upgraded the SQL Compare engine that powers SQL Release. For details see the SQL Compare 11.2 release notes.

Features

We've made more improvements to the Changes.html report that's created as part of the database deployment resources. All the information you need is now in one place. The report contains three tabs:

• Changes: shows schema and static data changes
• Warnings: shows warnings of potential data loss, such as if any objects will be dropped
• Script: shows the Update.sql script

We're working on further improvements to the report and we'll be releasing these soon. In the meantime, we'd love to hear what you think about the changes so far. Email your feedback to the DLM Automation Team.

1.2.1.2809 - June 10th, 2015

This release contains further improvements to the Changes.html report.

We've also upgraded the SQL Compare engine that powers SQL Release. For details see the SQL Compare 11.2 release notes.

Features

We've improved the Changes.html report that's created as part of the database deployment resources. The report now shows static data changes as well as schema changes.

We're working on further improvements to the report and we'll be releasing these soon. In the meantime, we'd love to hear what you think about the changes so far. Email your feedback to the DLM Automation Team.

Fix

• SQLREL-84: User-defined object types no longer incorrectly start with 'null' on the Changes.html report.

1.2.1.2726 - June 3rd, 2015

This release contains a new, improved version of the Changes.html report.

We've also upgraded the SQL Compare engine that powers SQL Release. For more details see the SQL Compare 11.2 release notes.

Features

We've improved the look and feel of the Changes.html report that's created as part of the database deployment resources. We now show:

• differences in a unified format that's more compact and easier to read
• color-coded highlighting of what'll be added, removed and modified once you deploy, so it's easier to see different types of changes

We're working on further improvements to the reports and we'll be releasing these soon. In the meantime, we'd love to hear what you think about the latest changes. Post your feedback on the UserVoice website.

Known issue

• SQLREL-84: User-defined object types currently start incorrectly with 'null' on the Changes.html report.

1.2.1.2643 - May 27th, 2015

Feature

Static data is now included in the SQL Release pre-deploy schema check. This check happens when you execute the Use-DatabaseRelease cmdlet, just before the update script runs.

For more details, see Deploying static data with SQL Release.

1.2.1.2602 - May 20th, 2015

We've upgraded the SQL Compare engine that powers SQL Release. 

For details of new features and bug fixes, see the SQL Compare 11.2 release notes.

1.2.0.2423 - April 22nd, 2015

This release contains improvements to the way our code manages licensing. These are internal changes that don't affect how the product works, so there aren't any differences between this version and the last.

1.2.0.2364 - March 31st, 2015

If you were a SQL Release beta user and want to keep using SQL Release after your beta version has expired, go to this page to download the DLM Automation Suite. You'll start a 28 day free trial once you start using any of the DLM Automation Suite tools. For installation instructions, see Installing.

If you have an existing SQL Automation Pack license, a serial number for the DLM Automation Suite has been generated for you. For details of how to upgrade, see Upgrading (DLM Automation Suite documentation).

Features

• We've created four SQL Release step templates to help you set up a database deployment project in Octopus Deploy. For more information, see Octopus Deploy step templates reference.
• We've added a new cmdlet that lets you activate your DLM Automation Suite license serial number. For more information, see Activating. 

Fixes

• SQLREL-68: SQL Database schema fill factor not handled correctly in the update script 
• SQLREL-73: ImportDatabase doesn't import source and target database descriptions correctly