Recursive MDX Query Rationalization for OLAP Size Limits

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing OLAP querying methods face challenges with long MDX queries due to redundant data and large numbers of columns and rows, often exceeding the size limits of multidimensional data sources.

Innovation Solution

A recursive rationalization process is employed to replace elements of the MDX query with generators, simplifying the query and reducing its size by using metadata to convert multiple objects into a more compact query format.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If MDX queries include enumeration over large lists of members to retrieve comprehensive data, then query completeness is improved, but query size exceeds system limits

Engineering Contradiction:
Improvequery completenessVSAvoidquery size
Core Design Contradiction:
ReliabilityVSLength of stationary object

Solution Approach 1:

The patent segments the large list of members into multiple smaller subsets or groups. Instead of including all members in a single enumeration, the query is divided into multiple smaller queries, each handling a subset of members. This segmentation allows the system to retrieve comprehensive data across all members while keeping each individual query within size limits imposed by the OLAP server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an additional dimension by adding a grouping or pagination parameter to the query structure. By organizing members into groups across multiple query executions (effectively adding a query iteration dimension), the system can handle large member sets without requiring a single oversized query. This transforms the problem from one dimensional (single large query) to multi-dimensional (multiple structured queries).

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If MDX queries select many columns and rows to ensure comprehensive data retrieval, then data coverage is improved, but query complexity and size increase

Engineering Contradiction:
Improvedata coverageVSAvoidquery complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and separates the member enumeration logic from the core query structure. By pulling out the large list of members and handling them through iterative processing or grouping mechanisms, the core query template remains simple and reusable. This extraction reduces query complexity by eliminating the need to embed massive member lists directly in each query while maintaining comprehensive data coverage.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a universal query template that can be applied repeatedly across different member subsets. Instead of creating unique complex queries for each member combination, a single parameterized query structure serves multiple purposes by accepting different member groups as parameters. This multi-functional approach reduces overall query complexity while ensuring comprehensive data retrieval across all members.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7698257B2Apparatus and method for recursively rationalizing data source queries
Publication Date: 2010.04.13 SAP IRELAND LTD
  • US7698257B2 patent drawing
  • US7698257B2 patent drawing
  • US7698257B2 patent drawing

AI summary

A computer readable medium stores executable instructions to receive a Multidimensional Expressions (MDX) query. The MDX query is recursively rationalized to form a rationalized query. The rationalized query is applied to a multidimensional data source to produce query results. The query results are returned.