Data Warehouse Trending - best practices on scheduling the job and using the data


Article ID: 196736


Updated On:


Clarity PPM On Premise


We are interested in enabling Data Warehouse Trend Reporting.

In order to be able to display the change of data over time, will we need to create separate trend snapshots instead of updating an existing trend snapshot? If our users want to see how data changes from month to month, would we create a new trend snapshot at the end of each month which captures the data for that specific month? We want to be able to make this data available, but want to ensure that we are setting up our jobs appropriately.


Release : All Supported Clarity releases



If you would like a new snapshot taken every month and being able to compare between them then our recommendation would be to schedule the Create Trend job every month. This will create a separate snapshot.

If you would like to update an existing snapshot, you can do that with the Update job, but this will erase the existing trend data. It doesn't seem like this is a good use case for you.

For more information check the documentation here:

Also check this KB that explains the jobs parameters:

The job can be scheduled in many ways, We recommend looking into the data after few runs and see the optimal use for you specifically.