Deployments

Deployments let you prepare and apply Oracle object changes and data migrations with a structured workflow. You can preview deployment definitions, choose DDL sources, save manifests, and restore generated backups when needed.

What Is a Deployment?

A deployment is a curated set of database objects, worksheet scripts, APEX exports, or table data migration entries that target one or more Oracle connections.

Creating a Deployment

1. Open the Deployments / Data migrations view.
2. Click Create new deployment or add selected objects from the Connections Explorer.
3. Add database objects, worksheet content, scripts, or table migration entries.
4. Choose the target connection and DDL source strategy for each entry.
5. Save the deployment manifest when you want to reuse the definition.

Previewing Changes

Before executing, use Preview deployment definition or open the deployment dialog to review:

• The object or script list
• Target connections and schemas
• Whether DDL comes from live metadata, local files, or a prefer-file fallback
• Data migration options such as batch size, commit interval, LOB batch size, and row-level error handling

When live DDL is selected, Nexo SQL Studio fetches current Oracle metadata before building the deployment.

Executing a Deployment

1. Review the preview and click Deploy.
2. A confirmation dialog shows the entire script list. Confirm to proceed.
3. Each entry is executed in order. Progress and status are shown per entry.
4. If an entry fails, execution stops with the database error and the generated backup remains available for restore flows that support it.

Deployment History

Saved deployment definitions include:

• The selected objects and scripts
• Target connection metadata
• DDL source strategy
• Data migration options
• Generated backup and restore metadata when available

Access saved definitions from the Deployments / Data migrations view.

Data Migration Settings

Tune data migration execution in VS Code settings:

Setting	Purpose
nexo-sql-studio.deploy.dataMigration.fetchSize	Rows fetched per source batch
nexo-sql-studio.deploy.dataMigration.batchSize	Rows written per batch
nexo-sql-studio.deploy.dataMigration.commitEveryRows	Commit interval during migration
nexo-sql-studio.deploy.dataMigration.batchErrors	Continue batch writes and report row-level errors

Offline DDL Export

Before deploying, you may want to export a local snapshot of current DDL for offline comparison. See Offline DDL Export.