...

Profiles the entire database to build an in-memory model.
Tests the changes against rules configured for the project at the intended step in the pipeline.
Simulates the change against the in-memory model and to show how will appear in the target database.

There are two forecast project settings:

Connections for forecast profiling in multi-schema projects:

For SQL Server, DB2, and Postgres only one connection is used to profile the managed schemas during forecast. The first schema will be profiled, then the second schema, then the third, etc.
For Oracle with Liquibase Enterprise/Datical versions 7.14 and higher, multiple connections are used to profile the managed schemas during forecast. A maximum of 10 connections are used to profile the first 10 schemas simultaneously. Note that you may notice higher CPU utilization due to multiple connections being used for Oracle forecast profiling with Liquibase Enterprise/Datical versions 7.14 and higher.

Overriding Project Options

...

Use the forecast command in the CLI. See the forecast command listing in /wiki/spaces/DDOC59/pages/795771831 CLI Commands for the options you can specify.

...

Code Block
hammer forecast Dev

Forecast Results

Forecast html reports are placed in datical/<project>/Reports, sorted by date.