Techniques for integrating disparate data access mechanisms

• US 8,108,335 B2
• Filed: 07/17/2007
• Issued: 01/31/2012
• Est. Priority Date: 07/17/2007
• Status: Active Grant

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: Teradata US, Inc. (Teradata Corporation)
• Inventors: Nolan, Ellen, Eschwege, Michael
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Black, Linh
• Application Number:
  US11/778,709
• Publication Number:
  US 20090024594A1
• Time in Patent Office: 1,659 Days
• Field of Search: 707/602, 707/708, 707/605, 707/791
• US Class Current: 707/602
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

Techniques for integrating disparate data access mechanisms are provided. A user attempts data access against an infocube and its data access mechanism. Transparently, that access attempt is translated into a format recognized and processed by a relational database access mechanism to produce results. The results are then translated from a relational database format back to an infocube format and presented to the user within the infocube'"'"'s data access mechanism.

Claims

1. A machine-implemented method, comprising:

receiving a search criteria via an infocube interface from a user, wherein the search query includes a time-dependent constraint, the search criteria is detected when the search criteria is initiated by the user via the infocube interface and a relational database service is initiated, the infocube interface is included with an infocube, the infocube is a customized package of information that includes its own internal data representation and the infocube interface for accessing that internal data representation;

automatically transitioning from the infocube interface to a relational database via the relational database service having a relational database interface;

using the relational database interface to search the relational database and to acquire an answer set that conforms to the search criteria having the time-dependent constraint; and

automatically translating the answer set to a data format used and recognized by the infocube interface and presenting to the user within the infocube interface, the infocube is a virtual infocube presents to the user as an actual infocube but actual data access is achieved via pointers and translations to a relational database backbone via the relational database interface, where the data actually resides and is manipulated on behalf of the user from the relational database.

2. The system of claim 1, wherein automatically transitioning further includes evaluating the search query for key figures and filtering criteria defined therein and querying metadata tables of the relational database to map infocube constructs found in the search criteria to relational database constructs.

3. The system of claim 2, wherein using further includes assembling the relational database constructs into a SQL query and processing the SQL query as the search against the relational database.

4. The system of claim 3, wherein assembling further includes producing the SQL query with a SELECT clause for characteristics and select aggregations of the key figures.

5. The system of claim 4, wherein assembling further includes producing the SQL query with a FROM clause that resolves a fact table and dimension tables that the SELECT clause is to process against.

6. The system of claim 5, wherein assembling further includes producing the SQL query with a WHERE clause that enforces the filtering criteria.

7. The system of claim 1, wherein automatically translating further includes wrapping the answer set with one or more SQL OUTER SELECT clauses to process transformation actions on the answer set and automatically place it in the data format used by the infocube interface.

8. A machine-implemented method, comprising:

receiving an infocube formatted query request for target data, an infocube is a customized package of information that includes its own internal data representation and includes an infocube interface for accessing the internal data representation, and the infocube formatted query request is directed to the infocube interface of the infocube;

evaluating the infocube formatted query request for key figures and characteristics, at least one key figure is a non-cumulative key figure;

searching metadata of a relational database for mappings to the key figures and the characteristics;

assembling a relational query using constructs found in the mappings to the metadata of the relational database;

processing the relational query against the relational database to receive an answer set; and

enforcing separate security at an infocube level of access from that which is associated with a relational database level of access, the infocube is a virtual infocube that presents to a user as an actual infocube but actual data access is achieved via pointers and translations to a relational database backbone via a relational database interface, where the data actually resides and is manipulated on behalf of the user from the relational database.

9. The method of claim 8 further comprising, translating the answer set from a relational database format to an infocube format.

10. The method of claim 9 further comprising, presenting the answer set in the infocube format to a user that initially made the infocube formatted query request within an infocube interface and within a context of a particular infocube.

11. The method of claim 8, wherein evaluating further includes evaluating the infocube formatted query request for filtering criteria and using the filtering criteria in assembling the relational query.

12. The method of claim 8, wherein evaluating further includes recognizing the characteristics as including one or more of the following attributes:

time constraints and hierarchical relationship constraints.

13. The method of claim 8, wherein evaluating further includes recognizing the key figures as quantifiable measures or values for the target data as defined by a user using an infocube interface.

14. The method of claim 8 further comprising:

receiving an update operation from a user in an infocube interface format for data defined within the infocube;

using the metadata to translate the operation to a relational database update operation for relational data that maps to the data; and

updating the relational data within the relational database in response to processing the relational database update operation.