...

• Please see the example MultiCatalog MSSQL .tsv files and details here: Creating a Datical Project Liquibase Enterprise Using the Project Creation Script (project_creator.groovy)

Representation in Project File

...

• Each SQL script is required to identify the database it is working on. You can provide the database names using these methods:
  • USE DATABASE statement for packaging scripts in ddl and , ddl_direct, and sql_direct folders (or for creating "Execute with sqlcmd for Microsoft SQL Server and Azure SQL databases" change sets in the GUI Change Set Wizard)
  • With deploy packager you could create a metadata.properties file that specifies schemaName as <databaseName>.<schema>
• Object references in a SQL script must be unambiguous. 
  • Use fully qualified object references: <schema>.<object>. 
  • Do not use unqualified object references:  <object>. 
  • External (cross-database) object references must be fully specified: <databaseName>.<schema>.<object>

...

During packaging, the database specified is used to add a USE <databasename> statement to the SQL files being packaged. 

Operations

Use the Datical DB CLI for managing the project and performing operations

• package (including backup, snapshot, and compare)
• status
• forecast
• deploy
• rollback

...