Introduction
When configuring a SQL Rule in the Modeler, you can enable post-execution actions that automatically deploy or process the OLAP database after the rule finishes executing successfully. These actions ensure that changes made by the rule are reflected in the cube without a separate manual step.
This article covers the six available post-execution actions, configured in the Process and Advanced tabs of the SQL Rule editor.
Process OLAP database
How to configure: In the SQL Rule editor, go to the Process tab and check Process OLAP database.
What it does: Fully processes all data partitions, dimensions, and hierarchies in the application so that all data is up to date in the cube. Operations run in parallel, making this faster than processing each object individually (which runs sequentially).
When to use it: The rule updates many dimensions, hierarchies, or MOLAP partitions.
Note: Users need to be an application admin or system admin in order to trigger this action.
Process dimension
How to configure: In the SQL Rule editor, go to the Process tab, click Add Process, and select Process Dimension. Then choose the dimension, member list, and process type.
What it does: Processes a specific dimension hierarchy in the OLAP cube so that dimension member changes are reflected. Each process item added runs sequentially. The process type determines the scope and speed of the operation:
- Process Add — Only adds new members. Fastest option, but cannot handle updates or deletes. Requires the dimension to already be in a processed state. Does not reprocess impacted cubes.
- Process Update — Reads all source data, adds new members, and updates existing member attributes and hierarchies. Handles adds and updates but not deletes. Does not reprocess impacted cubes.
- Process Full — Drops and rebuilds the entire dimension from scratch. Handles adds, updates, and deletes. Automatically reprocesses any impacted cubes since the full rebuild invalidates them. Slowest but most thorough.
When to use it: The rule adds, removes, or updates members in a specific dimension table (e.g., adding new cost centers or updating an account hierarchy). Choose the process type based on the type of change: Process Add for new members only, Process Update for new and modified members, or Process Full when members may be deleted.
Process partition
How to configure: In the SQL Rule editor, go to the Process tab, click Add Process, and select Process Partition. Then choose the model and partition.
What it does: Processes a specific data partition in the OLAP cube so that fact data changes are loaded. Each process item added runs sequentially.
When to use it: The rule inserts or updates fact data that flows into a specific model partition (e.g., loading actuals into a monthly partition).
Deploy security
How to configure: In the SQL Rule editor, go to the Advanced tab and check Deploy Security.
What it does: Regenerates all Kepion-related OLAP security roles based on current dimension security settings (including Active Directory sync), then processes security-related dimension hierarchies so the new roles take effect immediately.
When to use it: The rule modifies dimension security tables (e.g., user access to dimension members).
Deploy to OLAP
How to configure: In the SQL Rule editor, go to the Advanced tab and check Deploy to OLAP.
What it does: Performs a full redeployment in four sequential steps: relational schema → OLAP structure → security roles → full database processing.
When to use it: The rule makes structural changes (e.g., modifying dimension tables that affect the cube schema) or you need a guaranteed full sync between the relational database and the OLAP cube.
Note: Users need to have Application Administrator and/or Model Designer privileges in order to trigger this action.
Important: This option is mutually exclusive with the others. If checked, the system skips Process OLAP Database, Deploy Security, and Deploy MDX — the full redeployment already covers everything.
Deploy MDX
How to configure: In the SQL Rule editor, go to the Advanced tab and select one or more models under the Deploy MDX section.
What it does: Regenerates the MDX calculation scripts (calculated members, named sets, SCOPE statements, etc.) for the selected models and pushes them to the OLAP cube.
When to use it: The rule updates data or metadata referenced by MDX calculations — for example, updating application variable values used in an MDX rule.
Quick reference
| Option | What it does | When to use it |
|---|---|---|
| Process OLAP Database | Processes all partitions, dimensions, and hierarchies in parallel | Rule updates many dimensions/hierarchies or MOLAP partitions |
| Process Dimension | Processes a specific dimension hierarchy sequentially | Rule adds, removes, or updates members in a specific dimension |
| Process Partition | Processes a specific data partitions sequentially | Rule inserts or updates fact data in a specific partition |
| Deploy Security | Regenerates OLAP security roles and processes security dimensions | Rule modifies dimension security tables |
| Deploy to OLAP | Full redeployment (relational, OLAP structure, security, processing) | Rule makes structural changes or needs full sync |
| Deploy MDX | Regenerates MDX scripts for selected models | Rule updates data/metadata referenced by MDX calculations |
Note: Deploy to OLAP overrides all other options. Deploy Security and Deploy MDX only run when Deploy to OLAP is not checked.