Forecasting allows you to analyze the potential impact of changes before you deploy them. 

A forecast operation does the following:

• 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.

Overriding Project Options

You can override project settings by specifying different options, either in a GUI dialog or by specifying options on the CLI. 

Forecast Using the GUI

You can forecast directly or forecast with options. 

Forecast Only

1. Open the project in the GUI
2. Click the Plan tab. 
3. Click Forecast.
4. If runtime credentials are set for the project OR no credentials are entered for the step, you are prompted for the user name and password for the database. 

Forecast with Options

A dialog presents options to override. 

1. Open the project in the GUI
2. Click the Plan tab. 
3. Click Forecast with Options 
4. In Forecast Options, specify additional options, then click Finish. 
5. If runtime credentials are set for the project OR no credentials are entered for the step, you are prompted for the user name and password for the database. 

Forecast Using the CLI

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

The command requires a deployment step argument. The example uses Dev. 

hammer forecast Dev

Forecast Results

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

See /wiki/spaces/DDOC59/pages/795673737