System and method of multidimensional query results processing

• US 20050010566A1
• Filed: 05/27/2004
• Published: 01/13/2005
• Est. Priority Date: 05/27/2003
• Status: Active Grant

• Current Assignee: Congos Incorported, International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cosma, Marius, Cushing, David, Beffert, Helmut, Warner, Neil
• Granted Patent: US 9,081,849 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2423 Interactive query statement specification based on a database schema
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 16/902 using more than one table in sequence, i.e. systems with three or more layers

Abstract

A multidimensional query results processing system for translating output of an execution of a multidimensional query into a data result set that reflects the semantics of an entity/relationship schema report specification is provided. The system comprises a result set description generation module for producing a result set description that reflects the semantics of the report specification, a tabular row generation module for converting the results of the single multi-dimensional query into a collection of rows of data, a tabular summary level calculation module for calculating a summarization level of a row a data, a tabular header row generation module for producing a header row to include in the row of data, and a cross-tabulated result generation module for converting the results of the single multi-dimensional query into a result set that matches the semantics of the report specification.

Claims

1. A multidimensional query results processing system for translating output of an execution of a multidimensional query into a data result set that reflects the semantics of an entity/relationship schema report specification, the system comprising:

a result set description generation module for producing a result set description that reflects the semantics of the report specification;

a tabular row generation module for converting the results of the single multi-dimensional query into a collection of rows of data;

a tabular summary level calculation module for calculating a summarization level of a row a data;

a tabular header row generation module for producing a header row to include in the row of data; and

a cross-tabulated result generation module for converting the results of the single multi-dimensional query into a result set that matches the semantics of the report specification.

2. The system as claimed in claim 1, further comprising a translation module for converting the report specification into a multi-dimensional query.

3. The system as claimed in claim 2, further comprising an execution module for executing the multi-dimensional query.

4. A method of transforming results of a multidimensional query into results having the semantics of an entity/relationship schema report specification, the method comprising the steps of:

combining a result set description of a multi-dimensional query and rules of the entity/relationship schema to produce a final result set description;

converting results of the multi-dimensional query result set into a collection of rows of data;

producing headers for inclusion into the rows of data; and

converting results of the multi-dimensional query into a result set that matches the semantics of the entity/relationship report specification.

5. The method as claimed in claim 4, further comprising the step of producing a full stack of members representing a row of data, the step including:

pushing a highest-level member of a dimension onto a stack;

traversing parent/child relationships within a dimension along an edge to push each member at each level onto the stack;

popping a top member off the stack; and

pushing all siblings of the top member onto the stack.

6. The method as claimed in claim 4, further comprising the step of creating a header row, the step including:

setting a state of a header to header nested;

performing a check header nested;

performing a check header current;

performing a check header done;

performing a check children;

performing a check nested;

performing a check current;

performing a check sibling; and

performing a check ancestor.

7. The method as claimed in claim 4, further comprising the step of creating a header row, the step including:

setting a state of an element to header nested;

checking for nested dimensions until there are no more;

setting the state of the element to check header current;

filling the dimension with nested dimension fillers;

determining a summary level;

setting the state of the element to header done;

removing the nested dimension fillers;

checking all children of the element until there are no more children;

setting the state of the element to check nested;

determining if there are any nested elements;

filling a current dimension with nested dimension fillers;

setting the state of the element to check current;

determining a summary level;

setting the state of the element to check siblings;

moving the MDDS Iterator to the next sibling;

keeping a row copy; and

setting the state to check ancestor.

8. The method as claimed in claim 7, further comprising the steps of:

indicating a row has been found if the summary level is ≧

0;

deleting an element if there are other check header current states in the stack; and

setting the state to check header nested if there are more siblings in the state.

9. A computer data signal embodied in a carrier wave and representing sequences of instructions which, when executed by a processor, cause the processor to perform a method of transforming results of a multidimensional query into results having the semantics of an entity/relationship schema report specification, the method comprising steps of:

combining a result set description of a multi-dimensional query and rules of the entity/relationship schema to produce a final result set description;

converting results of the multi-dimensional query result set into a collection of rows of data;

producing headers for inclusion into the rows of data; and

converting results of the multi-dimensional query into a result set that matches the semantics of the entity/relationship report specification.

10. A computer-readable medium having computer readable code embodied therein for use in the execution in a computer of a method of transforming results of a multidimensional query into results having the semantics of an entity/relationship schema report specification, the method comprising steps of:

combining a result set description of a multi-dimensional query and rules of the entity/relationship schema to produce a final result set description;

converting results of the multi-dimensional query result set into a collection of rows of data;

producing headers for inclusion into the rows of data; and

converting results of the multi-dimensional query into a result set that matches the semantics of the entity/relationship report specification.

11. A computer program product for use in the execution in a computer of a multidimensional query results processing system for translating output of an execution of a multidimensional query into a data result set that reflects the semantics of an entity/relationship schema report specification, the computer program product comprising:

a result set description generation module for producing a result set description that reflects the semantics of the report specification;

a tabular row generation module for converting the results of the single multi-dimensional query into a collection of rows of data;

a tabular summary level calculation module for calculating a summarization level of a row a data;

a tabular header row generation module for producing a header row to include in the row of data; and

a cross-tabulated result generation module for converting the results of the single multi-dimensional query into a result set that matches the semantics of the report specification.