Page Comparison

...

Project Type	Characteristics
Single-schema	Manages only one schema Tracking tables are kept in the managed schema. Note: you can use a multi-schema project with only one schema if you want to keep the tracking tables separate from the managed database objects. Schema names can be different from step to step Cannot add schema
Multi-schema	Manages one to many schema. Convenient for Oracle databases. Limited to one database per project for other database types (SQL Server, DB2, EDB Postgres). Tracking tables can be assigned to a separate schema just for them. Note: this can be an advantage even for projects that require only one schema. Database type must be the same across release pipeline steps. For a list of database types, see Hardware, Software, and Database Requirements. Each row represents a database type. For example, EDB Postgres and PostgreSQL Community are different database types. Schema names must be the same across release pipeline steps Can add schema
Multi-database	SQL Server only Implicitly multi-schema as well Manages one to many databases. One to many schema can be managed in each database Tracking tables can be assigned to a separate schema just for them Schema names must be the same across release pipeline steps Can add databases Can add schema Most customers who use multi-database configuration use properties for schema names

Projects, Steps, and Schema

...