Extending Deployments with Procedure Call Operations
You can include one or more precoded procedures to customize your deployment. For example, you might want to configure the target server in some way such as enabling or disabling triggers or changing the server configuration. You do this by adding a procedure call operation to the deployment plan.
A procedure call operation requires a precoded, existing SQL script that can be run as part of the deployment plan. The procedure can contain any API call and other code that TDV supports but it cannot require any parameters. The procedure must reside on the TDV server where the Deployment Manager server is running.
When you add a procedure to a deployment plan, you need to specify the procedure name and where you want the procedure to execute: the source server, the target server, or the Deployment Manager server.
Note: Plan operations can’t be reordered, so be sure that any necessary procedure call operation is added before other operations in the plan that might require it.
To specify a procedure call operation with a deployment plan
1. Click PLANS and select a plan.
2. Click Edit.
3. On the Operations tab, click Add Operation.
4. Select Procedure Call Operation from the menu.
5. In the dialog that lists all procedures found on the TDV source, select a procedure and click OK.
Deployment Manager adds the Procedure Call operation to the Operations list with these properties:
Property | Description |
Procedure Path | Displays the path to this procedure in the source server. |
Execution Environment | • DM—Deployment Manager server • SOURCE—Source site server • TARGET—Target site server (default) |
6. Edit the Execution Environment if necessary. To edit this option, double-click the Execution Environment row, then select a different value.
7. Click Save.