Limited Forecast is a mode of Forecast that selectively profiles database objects based on the changes targeted for Deployment. This significantly reduces the time spent on the Forecast & Full Deploy.

Limited Forecast can be set as the default mode at the project level in the project settings or at the Deployment Step level with a simple check box.

Notes:

Because a full profile of the database is not created during Limited Forecast, some Post Forecast rules may be skipped because the objects they depend on are not present in the Post Deploy Model.
Associated objects for non-referenced tables are not profiled:
- primary keys
- columns
- indices
- check constraints
- foreign key constraints
- unique constraints

...

All table names are selected during Limited Profile. This gives Datical the capability of detecting duplicate object creations for non-referenced tables during Limited Forecast.
With versions 7.13 and above, in multi-schema projects, Limited Forecast will only profile the schemas that are relevant to the current deployment.
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.

How to set Limited Forecast

Specifying Limited Forecast on the project settings Settings tab
Specifying Limited Forecast on the Forecast With Options Screenscreen
Specifying Limited Forecast on the Deploy With Options Screenscreen
It can also be set from the command line using the "hammer set limitForecast true" command