DLM Automation 2.1 release notes
Published 25 April 2018
DLM Automation 2 drops support for the migrations V2 beta (in SQL Source Control prior to version 5)
Before upgrading, you need to ensure that all of your migrations created in the migrations V2 beta are deployed to every database in every environment. After upgrading, any migrations created with the beta will be ignored during deployment.
2.1.3 - June 6, 2018
- Updates SQL Compare and SQL Data Compare from 18.104.22.16823 to 22.214.171.12487
- Updates SQL Data Generator from 126.96.36.1992 to 188.8.131.529
- Updates SQL Doc from 184.108.40.2065 to 220.127.116.115
2.1.2 - May 21, 2018
- Updates SQL Compare and SQL Data Compare to 18.104.22.16823
2.1.1 - May 15, 2018
- The Import-DlmDatabasePackage cmdlet now supports importing zip archives
2.1.0 - April 25, 2018
The DLM Automation cmdlets are now available from Powershell Gallery
You can now download DLM Automation from the PowerShell Gallery using
the PowerShellGet functionality
built into PowerShell 5. For example, to install DLM Automation for the current user, run the following PowerShell:
IMPORTANT: Use of this functionality requires a SQL Toolbelt license.
If you are unsure of your current user license entitlement please contact .
Please see https://www.red-gate.com/DLMA/EULA/PowershellModule for full licensing terms.
Initial support for building and releasing ReadyRoll projects
You can now pass ReadyRoll
.sqlproj files into
and use the resulting objects through a DLM Automation pipeline. ReadyRoll projects will also work
with the various DLM Automation addons for CI systems.
Please note that the
cmdlets do not currently support ReadyRoll projects, and that many optional parameters on the other
cmdlets do not yet work for ReadyRoll pipelines. We will continue to add ReadyRoll support to DLM Automation in
- Added an optional OutputFormat parameter to Export-DlmDatabasePackage that allows to chose if the build artifact should be exported as a nuget package or a zip file
- The Documentation property of a DatabasePackage is now correctly displayed when the object is inspected in the console.
When you upgrade to DLM Automation 2, you will have to upgrade any add-ons you use.