SQL Change Automation PowerShell 3.0 release notes
Published 18 June 2018
3.0.7 - November 1, 2018
- Updates SQL Compare and SQL Data Compare to 13.6.3
- Updates SQL Doc to 4.1.1
- SCA-77: SQL Doc no longer fails with the error "Could not load file or assembly 'RedGate.BackupReaderInterfaces..." when documenting databases containing encrypted textual objects
- SCA-8: Fixed an issue where SQL Change Automation components could not be found when loading the PowerShell module from a network share.
3.0.6 - September 27, 2018
- Updates SQL Compare and SQL Data Compare to 13.5.1
- SCA-9 (SQLREL-142): Updated NuGet integration libraries to version 4.2, which should resolve some intermittent
ObjectDisposedExceptionerrors when publishing packages to NuGet repositories
3.0.5 - September 19, 2018
- When using SQL Change Automation projects, a new property is returned from
DriftStatus. Possible values:
Unknown. This property can be used to control whether or not to go ahead with a release when one or more objects in the target environment differ to the project baseline, which can happen when modifications have been made to a live environment. See the documentation for more information.
- Fixed an issue where the SQL Change Automation targets file could not be found when loading the PowerShell module from a network share.
- Fixed an issue where
New-DatabaseReleaseArtifactwould set the
DeployPathvariable in the script to a nonexistent directory.
3.0.4 - August 22, 2018
- Updates SQL Compare and SQL Data Compare to 13.4.8
- Adds a new release artifact for SQL Change Automation projects:
DriftRevertScript.sql. This script contains code to revert drift, as well as a commented section of code that can be copied and pasted into a new migration (allowing the drift to be incorporated back into project).
* Users of SCA projects will know this as the "resync" script that is produced during a patch build, as part of the drift analysis process.
- When using the
Use-DatabaseReleaseArtifactcmdlets with SQL Change Automation projects more detailed logging will be provided to the default output stream
Use-DatabaseReleaseArtifactwill now output a warning if the
xp_logeventcall used to log deployments to SQL Monitor fails, rather than silently ignoring the failure.
If you get this warning and don't want to use SQL Monitor integration, you can use the
-DisableMonitorAnnotationargument to stop
New-DatabaseReleaseArtifactcmdlet no longer raises an exception with SQL Change Automation projects when tables have drifted in the target environment
3.0.3 - July 12, 2018
3.0.2 - July 9, 2018
- When using SQL Change Automation projects, warnings are now logged when unsupported parameters are passed to the PowerShell cmdlets.
- For SQL Change Automation projects, added a new
SqlCmdVariablesparameter to the
New-DatabaseReleaseArtifactcmdlet, supporting SQLCMD variables with release-specific values.
- Added support for SQL Change Automation build artifacts to the
- Updates SQL Compare and SQL Data Compare to 22.214.171.12425
- Access SQL Change Automation release summaries (e.g. VSTS release summary) from SQL Monitor when it detects a SQL Change Automation release.
- URL is passed via new argument,
DatabaseReleaseArtifact, so this feature can be used with manual release processes too.
- Fixed an issue where VSTS extensions would log some verbose output even when not requested.
- Adds the
New-DatabaseProjectObjectcmdlet that provides the same functionality as the deprecated
New-DlmManualDatabaseSchemaValidation. The old cmdlet name will still work.
Use-DatabaseReleaseArtifact, add support for the
DisableMonitorAnnotationflag for SQL Change Automation projects.
3.0.1 - June 18, 2018
Initial release of SQL Change Automation, which replaces DLM Automation, and also
includes the functionality previously provided by ReadyRoll.
The SQL Change Automation PowerShell module provides cmdlets that allow you to automate building, testing, and deploying SQL Server databases. See the documentation for more information.
- Adds support for SQL Change Automation projects* in addition to SQL Source Control projects.
* SQL Change Automation projects were formerly known as ReadyRoll projects, and provide a migrations-based approach to database development.
SQL Change Automation is now available from the PowerShell Gallery to make it easier to configure automation environments.
All existing DLM Automation features and workflows continue to be supported. Existing scripts that use DLM Automation cmdlets will continue to work with the SQL Change Automation module.
The Octopus Deploy step templates for DLM Automation import the DLM Automation PowerShell module by name, which means they will not work if the tentacles are updated to SQL Change Automation. We will be releasing new versions of the step templates which support the SQL Change Automation module, but until then, don't upgrade any Octopus tentacles to SQL Change Automation.