Deploying database packages - Deployment Manager

If you are deploying an application and a database at the same time, we recommend that you add the database as the first deployment step.

There are two reasons for this:

• Failed database deployments are rolled back

  The SQL script Deployment Manager uses to deploy a database runs inside a transaction. If the scripts fails, any changes are rolled back automatically, and Deployment Manager does not perform the next deployment steps.

• Database deployments can take longer than application deployments

  While Deployment Manager is deploying multiple components, there will be a period of time when only part of a deployment has been completed. For example, if your web application package step is before your database package step, there will be a period during the deployment when the web site has been updated, but the database upgrade is still in progress. Database deployments can take a long time, so if you deploy the database first, you minimise the period of time when components are out of sync during the deployment.

Variables

To deploy database packages with Deployment Manager, you need to specify the following variables:

• databaseServer

  The SQL Server you want to deploy to.

• databaseName

  The database you want to deploy to.

You also need to specify how to connect to the SQL Server:

• databaseIntegratedAuthentication

  If you want to use Windows authentication to connect to the SQL Server, specify True. If you do not use Windows authentication, you need to also specify a username and password.

• databaseUserName

  The username you want to use to connect to the SQL Server. You do not need to specify a username if databaseIntegratedAuthentication is set to True.

• databasePassword

  The password to connect to the SQL Server. You do not need to specify a password if databaseIntegratedAuthentication is set to True.

Optionally, you can also specify:

• mode

  The type of upgrade you want Deployment Manager to perform. You can specify either upgrade if you want to upgrade the database, or createnew if you want to drop and recreate the database.

• allowDynamicDatabaseUpgrade

  If you want Deployment Manager to perform a dynamic database upgrade, specify True.

  However, Deployment Manager will always perform a static upgrade if the package contains an upgrade script it can use, even if this this variable is set to True.

  For more information, see: How Deployment Manager upgrades databases.

• allowPreDeployDatabaseValidation

  If you want Deployment Manager to validate the upgrade before deployment, specify True.

  Note that Deployment Manager can only validate a static upgrade (validating dynamic upgrades before deployment is not currently supported).

• allowPostDeployDatabaseValidation

  If you want Deployment Manager to validate the upgrade after deployment, specify True.

• abortOnHighSeverityWarnings

  If you want Deployment Manager to cancel a deployment if there are any serious deployment warnings, specify True.

Example: upgrading WidgetDev

For example, if we want to upgrade our WidgetDev database, we specify the following: