Order of Precedence

VLDB properties can be set at multiple levels, providing flexibility in the way you can configure your reporting environment. For example, you can choose to apply a setting to an entire database instance or only to a single report associated with that database instance.

The following diagram shows how VLDB properties that are set for one level take precedence over those set for another.

The arrows depict the override authority of the levels, with the report level having the greatest authority. For example, if a VLDB property is set one way for a report and the same property is set differently for the database instance, the report setting takes precedence.

Properties set at the report level override properties at every other level. Properties set at the template level override those set at the metric level, the database instance level, and the DBMS level, and so on.

A limited number of properties can be applied at each level.