Choosing Single-schema or Multi-schema

You should consider the flexibility that a multi-schema project offers you before choosing a single-schema project.

A single-schema project allows you to vary the schema name across steps in the release pipeline.
A multi-schema project allows you to do the following:
- Put the tracking tables in a different schema
- Add additional schemas later
- To vary the schema name across steps requires substitution parameters

Creating a Single-schema Project

Right-click on the left pane and select New > Deployment Plan.
Enter the Project name, then click Next. You accept the following default values:
- Single Schema - This project will manage 1 schema per Deployment Step
- Deployment Step - Select this when schema names differ across Deployment Steps
Enter the Name for the step, select the Database Platform, then click Next
Enter the database connection information, then click Test Connection.
Click Finish.

Note that you need to add steps to the project to complete it.