Abstract: A computer-implemented method, system and computer program product for improving performance for retrieving and reporting information from a data warehouse. A query (e.g., SQL query) is received. If a materialized view is present, and if such a materialized view was generated within the designated time frame, then the query is translated to query a materialized view. The translated query is then sent to a first data storage database of the data warehouse storing materialized views to be processed to obtain the materialized object associated with the query. If, on the other hand, the materialized view is not present, or the materialized view is present but has not been generated within the designated time frame, then the query is sent to the second data storage database of the data warehouse storing the original data without any modification to retrieve and report the appropriate information from the second data storage database.

Abstract: A computer-implemented method, system and computer program product for improving performance for retrieving and reporting information from a data warehouse. A query (e.g., SQL query) is received. If a materialized view is present, and if such a materialized view was generated within the designated time frame, then the query is translated to query a materialized view. The translated query is then sent to a first data storage database of the data warehouse storing materialized views to be processed to obtain the materialized object associated with the query. If, on the other hand, the materialized view is not present, or the materialized view is present but has not been generated within the designated time frame, then the query is sent to the second data storage database of the data warehouse storing the original data without any modification to retrieve and report the appropriate information from the second data storage database.

Abstract: Techniques are described for generating a hierarchical group based on a set of data. In one example, a method includes classifying two or more data items from a set of data with respect to a library of ontological concepts. The method further includes classifying the two or more data items with respect to lexical correlations between the two or more data items. The method further includes generating a hierarchical group in which the two or more data items are partitioned into one or more hierarchical partitions based at least in part on the classifying with respect to the library of ontological concepts and the classifying with respect to the lexical correlations, wherein each of the one or more hierarchical partitions comprises the two or more data items.

Abstract: Systems and methods may automate management of natural language queries of enterprise data. In one example, a method includes performing natural language processing and semantic processing on a natural language query to identify data sets relevant to the natural language query. The method further includes grouping the data sets into one or more query domains based at least in part on one or more relationships among the data sets. The method further includes prioritizing the query domain sets. The method further includes loading one or more of the query domain sets in an order based on the prioritizing of the query domain sets.

Abstract: Techniques are described for modeling hierarchical information from a data source. In one example, a method for modeling hierarchical information from the data source includes outputting for display a plurality of columns that represent corresponding data sets in the data source and each comprise values from the corresponding data set. The method further includes receiving an input indicating a selected value from a first column that corresponds to a first data set in the data source, and the selected value is comprised in the first data set. The method further includes receiving an input indicating a second column that corresponds to a second data set from the data source. The method further includes outputting for display a filtered view of the second column that comprises a subset of values from the second data set that are associated in the data source with the selected value in the first data set.

Abstract: Techniques are described for automated management of natural language queries of enterprise data. In one example, a method includes performing natural language processing and semantic processing on a natural language query to identify data sets relevant to the natural language query. The method further includes grouping the data sets into one or more query domains based at least in part on one or more relationships among the data sets. The method further includes prioritizing the query domain sets. The method further includes loading one or more of the query domain sets in an order based on the prioritizing of the query domain sets.

Abstract: Techniques are described for modeling business intelligence data. In one embodiment, a computer program product comprising a computer-readable storage medium has program code embodied therewith. The program code is executable by a computing device to receive one or more use cases, the use cases comprising semi-additive data; use case-based reasoning to identify one or more patterns in the data; and generate an aggregation model based on the identified pattern(s).

Abstract: Techniques are described for generating a hierarchical group based on a set of data. In one example, a method includes classifying two or more data items from a set of data with respect to a library of ontological concepts. The method further includes classifying the two or more data items with respect to lexical correlations between the two or more data items. The method further includes generating a hierarchical group in which the two or more data items are partitioned into one or more hierarchical partitions based at least in part on the classifying with respect to the library of ontological concepts and the classifying with respect to the lexical correlations, wherein each of the one or more hierarchical partitions comprises the two or more data items.

Abstract: A database interface for generating drill-through pats for various data cubes, derived from different report generating applications is disclosed. The interface comprises: (a) means for accepting a request from a user for data; (b) means for translating the request into a drill-through path selected from a plurality of possible drill-through paths between a source and a target; (c) means for applying one or more parameters to the selected drill-rough path to produce a valid drill-through path and to transfer the requested data over the valid drill-through path to an application; and (d) display means for displaying the requested data to the user.

Abstract: Techniques are described for modeling hierarchical information from a data source. In one example, a method for modeling hierarchical information from the data source includes outputting for display a plurality of columns that represent corresponding data sets in the data source and each comprise values from the corresponding data set. The method further includes receiving an input indicating a selected value from a first column that corresponds to a first data set in the data source, and the selected value is comprised in the first data set. The method further includes receiving an input indicating a second column that corresponds to a second data set from the data source. The method further includes outputting for display a filtered view of the second column that comprises a subset of values from the second data set that are associated in the data source with the selected value in the first data set.

Abstract: A model edit control system controls editing of a data model. A model repository manager allows multiple users to copy a stored model stored in a repository for executing changes on multiple model copies in parallel. An action log manager crates a model action log for the stored model and tracks actions executed on the stored model. The action log manager also creates a current action log for each model copy to record actions executed on the model copy. A model merger manager merges the model copies into the stored model in the repository, by playing the actions in the current action log against the stored model in the repository.

Abstract: A diagram manager has a diagram handler and a lineage handler. The diagram handler presents to a user a diagram representing relations between query subjects in a metadata model. The lineage handler changes presentation of a selected query subject to show one or more corresponding query subjects that are represented by the selected query subject.

Abstract: A model edit control system controls editing of a data model. A model repository manager allows multiple users to copy a stored model stored in a repository for executing changes on multiple model copies in parallel. An action log manager crates a model action log for the stored model and tracks actions executed on the stored model. The action log manager also creates a current action log for each model copy to record actions executed on the model copy. A model merger manager merges the model copies into the stored model in the repository, by playing the actions in the current action log against the stored model in the repository.

Abstract: The invention, when incorporated in a drill-through modeling tool (DMT), allows all the elements affecting drill-through behavior to be aggregated in a single structure or set of structures, thereby allowing administration to be simplified, and also permitting easier integration with third-party tools. The invention also provides for graphical displays of drill-through paths for a DMT user. These displays show the parameters and dependencies of each drill-through path and allow tool users to obtain a quick overview of the drill-through network and further, they allow the tool user to confirm drill-through dependencies at a glance. Drill-through objects may thus be manipulated and maintained in a graphical manner.

Abstract: A diagram manager has a diagram handler and a lineage handler. The diagram handler presents to a user a diagram representing relations between query subjects in a metadata model. The lineage handler changes presentation of a selected query subject to show one or more corresponding query subjects that are represented by the selected query subject.

Abstract: A system for data modelling is provided. The system comprises a model repository for storing one or more data models, a model partitioning module for segmenting a data model into smaller data models, and a model linking module for connecting two or more data models stored in the model repository.

Abstract: An impact analysis system for determining impact of a change to a data model is provided. The impact analysis system comprises a model comparison module for determining the differences between a published model and a modified model, a report generator for generating a report of the modified model, and a report comparison module for comparing a report of the published model with the report of the generated model.

Abstract: A database interface for generating drill-through pats for various data cubes, derived from different report generating applications is disclosed. The interface comprises: (a) means for accepting a request from a user for data; (b) means for translating the request into a drill-through path selected from a plurality of possible drill-through paths between a source and a target; (c) means for applying one or more parameters to the selected drill-rough path to produce a valid drill-through path and to transfer the requested data over the valid drill-through path to an application; and (d) display means for displaying the requested data to the user.

Abstract: The invention, when incorporated in a drill-through modeling tool (DMT), allows all the elements affecting drill-through behavior to be aggregated in a single structure or set of structures, thereby allowing administration to be simplified, and also permitting easier integration with third-party tools. The invention also provides for graphical displays of drill-through paths for a DMT user. These displays show the parameters and dependencies of each drill-through path and allow tool users to obtain a quick overview of the drill-through network and further, they allow the tool user to confirm drill-through dependencies at a glance. Drill-through objects may thus be manipulated and maintained in a graphical manner.