- one data node that contains in-memory data and for which Sign-Off features are enabled
- one DirectQuery data node
Option 1: Adjustment fields not present
In this case, the DirectQuery database is used without any modifications to its schema. In this setup, to enable horizontal distribution on the data node, use the following configuration for the DirectQuery data node, in addition to the settings already defined:
For a Sign-Off deployment, the Adjustments and Sign-Off hierarchies are present in the Cube configuration.
Therefore, those hierarchies must also be present in the Cube’s definition on the DirectQuery data node to make horizontal distribution possible.
To achieve this, in the Cubes using DirectQuery, a “dummy” Sign-Off hierarchy and a regular
Adjustments hierarchy are created, using the values in the DirectQuery database for the Source and Input Type levels of the hierarchy.
Option 2: Adjustment fields are present
In this case, the DirectQuery database is used with additional fields in the tables where adjustments can be present. You have to add the following fields:SOURCE: Sign-Off adjustment source tagging (for example, user input)INPUT_TYPE: type of the adjustment entry (for example, reversal)
By default, the you need to add the fields to the following tables:
TRADEPNLSTRADEPNLS_VECTORTRADE_SENSITIVITIESTRADE_SENSITIVITIES_VECTORPNL