Typical workflow
- Start Atoti Market Risk in in-memory mode and load the dataset you want to migrate.
- Call the migration helper endpoints to produce the DDL and CSV files (see below).
- Apply the DDL to your target database and load the CSV files.
- Restart Atoti Market Risk with the DirectQuery profile pointing at the now-populated database (see Getting started).
Endpoints
The controller is mounted athost:port/mr-application/migrationHelper/ and exposes:
Names are mapped through MrDirectQueryNameMapper, so tables and columns in the generated DDL follow the same convention as the runtime DirectQuery schema (e.g.
TradePnLs → TRADEPNLS, not TRADE_PN_LS).
The following stores are excluded from the generated schema by default (see MRMigrationHelperRestController.getDefaultExtractionBuilder()):
- Parent-child stores:
BookParentChild,CounterpartyParentChild,LegalEntityParentChild— these are used to populate their hierarchy stores and are not needed in the DQ schema. - Summary cube base stores:
BaseStore,SensiBaseStore,PnLBaseStore— summary cubes are not supported under DirectQuery. - The WhatIf simulation persistence table.
- Sign-off companion stores for
TradePnLs,TradeSensitivities,PnL.
MRMigrationHelperRestController and override getDefaultExtractionBuilder().
Configuration properties
Example: