Walk through the same change script creation and pipeline screens your team uses to promote database changes from DEV to QA to PROD.
The tour begins in the New Change Script window: name the change, choose the flow, add context, and paste or upload the SQL script.


The pipeline enforces approvals, captures stage-level evidence, and keeps rollback and recovery paths ready when execution fails.
Require approvals per stage and keep approver identity and approval history visible before promotion continues.
Run change scripts against one or many stage targets and inspect results for each connection from the same workflow.
Use rollback scripts and status-driven recovery states, with monitor logic for stuck change scripts and failure handling.