Deploying changes to a step in the release pipeline applies the changes to the database at that step.
...
| Option | Default | Description |
|---|---|---|
| None - no contexts are specified for deployment. | List of contexts to use. Use $all to specify all contexts configured on the project. |
| None - no labels are specified for deployment. | List of labels to use. Use $all to specify all labels configured on the project. |
| Deployment Mode | ||
| Full Deploy | Full Deploy includes a forecast (rules and change simulation). Quick Deploy deploys changesets without a forecast. |
| SQL Generation | ||
| False | Generate and save the SQL script used to deploy these changes. |
| False | Generate and save the SQL script to use to roll back these changes. |
| Collect Row Counts During Forecast and Deploy | ||
| False | Collect accurate row counts using table scan. This method may be time consuming for large tables |
| False | Collect estimated row counts using statistics. Uses database statistics as the source of information. You need to make sure the statistics are available and updated. The time saved varies, but can be significant for very large tables. |
| True | Do not collect row counts. |
| Limited Forecast | ||
| False | If set to true, limit forecasting to only those objects affected by the changes. Otherwise profile all objects in the target database schema. Note that some forecast and post-forecast rules may be skipped when this is true. |
| Stored Logic Validity Check | ||
| True (fail) | Determines what to do when the Stored Logic Validity Check fails. Both existing objects already in the database and new objects being deployed are checked.
|
...