SQL Release

SQL Release 1.0 release notes

1.0.7 - February 13th, 2015


SQL Release now includes additional checks when comparing and deploying schemas:

  • After running the update script to change the target database, SQL Release runs an additional post-deploy check to ensure that the static data in the database is now the same as in the source.
  • When specifying multiple databases as the value of -BeforeUpdate, SQL Release checks that the static data is the same in each before generating the database update object.
    See Deploying static data with SQL Release 
  • Before deploying changes, SQL Release checks if the target database is already in the desired state (that is, it has already been updated). If so, it skips the deployment.

Other changes

  • New-DatabaseUpdate no longer supports multiple input to the AfterUpdate parameter.

Known issues

  • SQLREL-60: Filters are not respected when comparing static data between -BeforeUpdate values.

Licences for this version will expire on 4th May 2015

1.0.6 - January 8th, 2015


You can now change whether SQL Release sends feature usage data and error reports to Redgate. This information helps us prioritize future development work and fix issues.

During installation, turn off the relevant check boxes in the installation wizard. For unattended installations see Installing from a command prompt.

Licenses for this version will expire on 8th April 2015

1.0.5 - December 5th, 2014


SQL Release will now apply changes in static data when creating an update from a package or scripts folder. 

See Deploying static data with SQL Release

Licenses for this version will expire on 26th February 2015

1.0.4 - November 27th, 2014


License for this version of beta will end on 26th February 2015

1.0.3 - November 13th, 2014


  • The SQL Compare options used when generating update scripts and running pre-deploy and post-deploy schema checks have changed. 
    For more information, see default comparison behavior used by SQL Release.

  • The New-SchemaSnapshot cmdlet has been removed.

1.0.2 - November 7th, 2014


  • The expiry date of the Beta is now logged when running SQL Release. A warning will be shown when the Beta is due to expire in a month.


  • SQLREL-51: Fixed a bug which may have caused interference with licensing of other Redgate products. 

1.0.1 - October 30th, 2014


  • Filters - SQL Release will apply the filters you have specified in SQL Source Control to include/exclude objects when generating the update script. The filters are also applied in the schema checks before creating an update script, where multiple sources have been specified, and in the schema checks before and after running the update script against a database.

    • SQL Release will apply filters when it finds a Filter.scpf file in the NuGet package or scripts folder you are using as the -AfterUpdate schema source. Filter.scpf is the standard filter file output by SQL Source Control. You can override this filter file using the -FilterPath parameter in the New-DatabaseUpdate cmdlet, to specify a different filter file.
  • SQL Release entry is added to the Start menu after installation, which opens the getting started documentation.
  • Feature usage data is collected and sent to Redgate. This data tells us which SQL Release cmdlets you are using, and will help us prioritize new features. 

    • If you want to stop sending this data, please email us.

Known issues

  • SC-7602: Dependencies are pulled in that should be excluded by filters.

1.0.0 - October 6th, 2014

This was the first release of SQL Release.


  • Create the resources needed to deploy your database changes, including the update script, a summary of changes, and any data loss warnings (New-DatabaseUpdate)

  • Review the update script, summary of changes and warnings before deploying (Export-DatabaseUpdate)

  • Check, before the deployment, that the target database hasn’t changed since update script was created (Publish-DatabaseUpdate)

  • Deploy the database changes to target databases (Publish-DatabaseUpdate)

  • Check, after the deployment, that the target databases have the correct schema (Publish-DatabaseUpdate)


Didn't find what you were looking for?