SQL Automation Pack

SQL Automation Pack 1.1.2 release notes

Warning

SQL Automation Pack v1.1.x.x releases contain a rewritten version of SQL CI which is not compatible with 1.0.x.x versions. If you're upgrading from a 1.0.x.x version, you must reconfigure your existing SQL CI build steps after installation. For details of how to upgrade, see Upgrading.

1.1.2.2238 - January 8th, 2015

This release contains new versions of SQL CI, SQL Packager and SQL Compare.

SQL CI 2.0.1.641

There are changes to the SQL CI command line, TFS Build plugin, TFS MSBuild scripts and TeamCity plugin. These include improvements to authentication security, and the ability to edit settings for sending error reports and feature usage data to Red Gate. 

Authentication details obfuscated

If you enter SQL Server authentication credentials while configuring SQL CI, your passwords are obfuscated. This fixes issue SQLCI-211.

Edit error reporting and feature usage data settings

You can change the settings that control whether to send SQL CI error reports and feature usage data (FUR) to Red Gate. These are sent by default. 

If you're using the SQL CI command line, TFS Build plugin or TFS MSBuild scripts, you can change the settings during or after installation. During installation, turn off the relevant check boxes on the installation wizard. Once installed, you can edit the registry key:

  1. Open the Registry Editor.
  2. Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL CI to display the SendErrorReports and SendFeatureUsageData values.
  3. Set the values to 0 to stop sending data, or 1 to send it.

If you're using the TeamCity plugin, error reports and feature usage data will be sent by default unless you change the settings after installation:

  1. Go to TeamCity's Administration page.
  2. Under Integrations, click Red Gate SQL CI Settings.
  3. Edit the Send error reports to Red Gate and Send feature usage data to Red Gate check boxes.

SQL Packager 8

SQL Packager 7 was retired in December 2014. This version of the SQL Automation Pack contains SQL Packager 8, which is a simplified version of the tool that works with any version of SQL Server.

For more information, see SQL Packager 8 documentation

SQL Compare 11.1.1.8

This version of the SQL Automation Pack contains the latest version of SQL Compare as of the 8th January 2015. 

1.1.2.2179 - November 4th, 2014

This release contains a new version of SQL CI (v2.0.1.564).

Exclude SQL Compare command line options

You can now exclude default SQL Compare command line options from the SQL CI build, sync and test steps. The default options are:

  • DecryptPost2KEncryptedObjects
  • IgnoreFillFactor
  • IgnoreWhiteSpace
  • IncludeDependencies
  • IgnoreFileGroups
  • IgnoreUserProperties
  • IgnoreWithElementOrder
  • IgnoreDatabaseAndServerName

The sync step also includes the IgnoretSQLt option.

To exclude options, enter the option name prefixed with a minus sign:

  •  If you're using the SQL CI command line, use the /additionalCompareArgs command and enter "options:-<option_name>". For example:

    /additionalCompareArgs="/options:-IncludeDependencies,-IgnoreWhiteSpace"
  • If you're using the SQL CI TeamCity plugin, on the Build Steps pages under Advanced options > Additional parameters, enter /options:-<option_name>.
  • If you're using the SQL CI TFS Build plugin, on the build, test or sync step Advanced tab under Include SQL Compare arguments, enter -<option_name>
  • If you're using the SQL CI TFS MSBuild scripts, in the build, test or sync properties files, enter <additionalCompareArgs>-<option_name></additionalCompareArgs>

    <additionalCompareArgs>-IncludeDependencies,-IgnoreWhiteSpace<additionalCompareArgs>

For more information, see Using the sqlCI.exe command line in SQL Automation Pack v1.1 and later.

1.1.2.2155 - October 15th, 2014

This release contains a new version of SQL CI (v2.0.1.555). It adds support for publishing SQL Test results to the SQL CI TFS Build plugin for Visual Studio. It also includes a couple of bug fixes.

Display SQL Test results using MSTEST Publish option

The option converts your JUnit XML test reports to MSTest TRX fomat and displays the SQL Test results as part of the Build Summary in Visual Studio.  

If you want to publish test results in MSTest format, you'll need Visual Studio Premium, Ultimate or Test Pro installed on the machine running your build agent.

Fixes

  • SQLCI-189: During SQL CI Build and Test step, create the temporary database using source SQL Server collation rather than default collation. 
  • SQLCI-226: Show the SQL statement and object when the SQL CI Build, Test or Sync step fails. 


Didn't find what you were looking for?