Patent Grant
7970728
Embodiments of the invention generally relate to databases. More specifically, embodiments of the invention relate to techniques for building and populating data marts with data from data repositories.
Data warehouses have become ubiquitous over the past two decades as means of providing an enterprise with decision support systems to identify trends and to execute strategic planning. Data marts constructed with fact tables and dimensional data models lie at the heart of such systems because such data marts offer a flexible and high-performance way to perform business analytics.
A significant cost in building such data marts lies in constructing the fact and dimension tables with a schema and with data from the different operational systems that contribute to the overall data warehouse content. In a typical approach, the IT staff builds a dimensional data model using a modeling tool of some kind, such as DB2 Warehouse Edition, Cognos Framework Manager, or Hyperion Essbase. This model often consists of a fixed set of facts, hierarchies and dimensions. For example, a retail store might build a fact table that contains data about its transactions, with dimensions based on store, time, and product.
Once the model is designed, it can be used to build and populate a data mart with data such that the dimensions and hierarchies can be used to efficiently query that data. However, the dimensional model itself is typically fixed in the definition of the hierarchies, the number of levels in the hierarchies, and the number of dimensions. This makes it difficult to change the dimensional model when the enterprise makes changes to the structure of the operational systems that populate the warehouse. Further, once the data is migrated to the new model, the old model is often lost, making it difficult to maintain a historical perspective of the warehouse data.
One embodiment of the invention includes a computer-implemented method for dynamically building and populating a data mart with data from a data repository. The method may generally include receiving a user configuration that specifies a data repository and an asset type in the data repository; generating a schema for an intermediate data warehouse for storing data relevant to the asset type, wherein the data relevant to the asset type comprises all measures for all assets of the asset type; populating the intermediate data warehouse by querying the data repository for the data relevant to the asset type; generating a schema for a data mart corresponding to the asset type; and populating the data mart by querying the intermediate data warehouse for the data relevant to the asset type.
Another embodiment of the invention includes a computer-readable storage medium containing a program which, when executed, performs an operation for dynamically building and populating a data mart with data from a data repository. The operation may generally include receiving a user configuration that specifies a data repository and an asset type in the data repository; generating a schema for an intermediate data warehouse for storing data relevant to the asset type, wherein the data relevant to the asset type comprises all measures for all assets of the asset type; populating the intermediate data warehouse by querying the data repository for the data relevant to the asset type; generating a schema for a data mart corresponding to the asset type; and populating the data mart by querying the intermediate data warehouse for the data relevant to the asset type.
Still another embodiment of the invention includes a system having processor and a memory containing a program, which when executed by the processor is configured to perform an operation for dynamically building and populating a data mart with data from a data repository. The operation should generally include receiving a user configuration that specifies a data repository and an asset type in the data repository; generating a schema for an intermediate data warehouse for storing data relevant to the asset type, wherein the data relevant to the asset type comprises all measures for all assets of the asset type; populating the intermediate data warehouse by querying the data repository for the data relevant to the asset type; generating a schema for a data mart corresponding to the asset type; and populating the data mart by querying the intermediate data warehouse for the data relevant to the asset type.
Yet another embodiment of the invention includes a computer-implemented method for dynamically building and populating a data mart with data from a data repository. The method may generally include receiving user configuration input that specifies the plurality of data repositories and a plurality of asset types in the plurality of data repositories, wherein the specified plurality of data repositories contain: (i) a plurality of assets of the specified plurality of asset types; (ii) at least one association between assets of two asset types; (iii) at least one asset group that groups assets based on the at least one association between two asset types; and (iv) a plurality of measures of at least one measure type, wherein the plurality of measures contain values that describe the plurality of assets; generating a schema for an intermediate data warehouse for storing data relevant to the specified plurality of asset types, wherein the data relevant to the specified plurality of asset types comprises (i) measures for measure types for assets of the specified plurality of asset types; (ii) at least one association between an asset of one asset type of the specified plurality of asset types and an asset of another asset type of the specified plurality of asset types; and (iii) at least one asset group that groups assets of the specified plurality of asset types; and wherein the schema for the intermediate data warehouse comprises a timestamp to allow versioning of records in the intermediate data warehouse; populating the intermediate data warehouse by querying the specified plurality of data repositories for the data relevant to the specified plurality of asset types; generating, for each asset type of the specified plurality of asset types, a schema for a data mart corresponding to the respective asset type; wherein the schema for the data mart comprises (i) a static dimension representing measure types and (ii) a static dimension representing time to allow versioning of records in the data mart; wherein a static dimension is a dimension that exists in each of the plurality of data marts; and populating, for each asset type of the specified plurality of asset types, the data mart corresponding to the respective asset type by querying the intermediate data warehouse for the data relevant to the respective asset type.
Another embodiment of the invention includes a computer-readable storage medium containing a program which, when executed, performs an operation for dynamically building and populating a data mart with data from a data repository. The operation may generally include receiving user configuration input that specifies the plurality of data repositories and a plurality of asset types in the plurality of data repositories, wherein the specified plurality of data repositories contain: (i) a plurality of assets of the specified plurality of asset types; (ii) at least one association between assets of two asset types; (iii) at least one asset group that groups assets based on the at least one association between two asset types; and (iv) a plurality of measures of at least one measure type, wherein the plurality of measures contain values that describe the plurality of assets; generating a schema for an intermediate data warehouse for storing data relevant to the specified plurality of asset types, wherein the data relevant to the specified plurality of asset types comprises (i) measures for measure types for assets of the specified plurality of asset types; (ii) at least one association between an asset of one asset type of the specified plurality of asset types and an asset of another asset type of the specified plurality of asset types; and (iii) at least one asset group that groups assets of the specified plurality of asset types; and wherein the schema for the intermediate data warehouse comprises a timestamp to allow versioning of records in the intermediate data warehouse; populating the intermediate data warehouse by querying the specified plurality of data repositories for the data relevant to the specified plurality of asset types; generating, for each asset type of the specified plurality of asset types, a schema for a data mart corresponding to the respective asset type; wherein the schema for the data mart comprises (i) a static dimension representing measure types and (ii) a static dimension representing time to allow versioning of records in the data mart; wherein a static dimension is a dimension that exists in each of the plurality of data marts; and populating, for each asset type of the specified plurality of asset types, the data mart corresponding to the respective asset type by querying the intermediate data warehouse for the data relevant to the respective asset type.
So that the manner in which the above recited features, advantages and objects of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings.
It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
Embodiments of the invention provide techniques for building and populating data marts with data from data repositories. Specifically, embodiments of the invention provide techniques to dynamically construct and populate data marts with dimensional data models from a set of data repositories that contain factual and association information about a set of related information assets. In one embodiment, an information asset, or simply an asset, is an entity described by a set of facts and associations to other assets. Facts may be attributes (strings), simple measures (observed numeric values; may also be strings), and complex measures, a.k.a. scores (computed numeric values), according to one embodiment of the invention. In one embodiment, a data mart is an instance of one or more snowflake schemas populated with data. Without loss of generality, it may be assumed that a data mart is made up of one snowflake schema; it is a straightforward extension to group multiple snowflake schemas into a data mart. In one embodiment, the dimensions, hierarchies, and fact tables of the data marts are dynamically derived from the asset data and associations of the data repositories. Further, the dimensions, hierarchies, and fact tables may change over time. According to one embodiment, the data marts accurately reflect the structure at any given point in time.
In one embodiment, an intermediate data warehouse is generated to process the facts and associations about each asset. In one embodiment, a warehouse is a database that contains asset data (facts and associations) collected at various points in time from a variety of data repositories. The intermediate data warehouse captures all relevant data from the data repositories that store information about assets. Information about assets includes facts about the assets and how the assets are related to each other. New facts may be added to the data repositories over time, and associations between assets may change over time.
In one embodiment, a technique is provided for automatically generating one or more data marts based on the intermediate data warehouse. The generated data marts allow a user to perform analysis over the assets and their associations to each other at any given point in time. In a particular embodiment, data marts are built by generating snowflake schemas (or star schemas) for the assets such that (i) the facts are used to populate a fact table; and (ii) the associations are used to populate dimensions and to create hierarchies. In one embodiment, a snowflake schema is a database schema definition such that centralized fact tables are connected to multiple dimensions. In one embodiment, a star schema is a specialization of a snowflake schema in which the dimensions are represented in a single table.
In one embodiment, data marts are defined and populated automatically rather than through a set of manual steps undertaken by a warehouse developer. Information about the assets described by the data marts may be extracted from several different repositories. For example, some information about the assets may be stored in one or more relational databases, while other information may come from an asset repository or a file system. Schemas for data marts are automatically derived from assets and associations in the data repositories. Each snowflake schema or star schema is constructed dynamically and includes facts, dimensions, and hierarchies. Hierarchies are defined for every derived dimension and may be balanced, unbalanced, or ragged based on the associations detected in the assets.
One embodiment preserves a historic view of the data retrieved from the underlying data repositories. Thus, while some of the data repositories may only keep a single state of the data (e.g., the most current state), the intermediate data warehouse schema may show a progression of the asset state over time and across different repositories. In this way, a user may access previous versions of the data retrieved from the underlying data repositories.
In the following, reference is made to embodiments of the invention. However, it should be understood that the invention is not limited to specific described embodiments. Instead, any combination of the following features and elements, whether related to different embodiments or not, is contemplated to implement and practice the invention. Furthermore, in various embodiments the invention provides numerous advantages over the prior art. However, although embodiments of the invention may achieve advantages over other possible solutions and/or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the invention. Thus, the following aspects, features, embodiments and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to “the invention” shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s).
One embodiment of the invention is implemented as a program product for use with a computer system. The program(s) of the program product defines functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive) on which information is permanently stored; (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive) on which alterable information is stored. Such computer-readable storage media, when carrying computer-readable instructions that direct the functions of the present invention, are embodiments of the present invention. Other media include communications media through which information is conveyed to a computer, such as through a computer or telephone network, including wireless communications networks. The latter embodiment specifically includes transmitting information to/from the Internet and other networks. Such communications media, when carrying computer-readable instructions that direct the functions of the present invention, are embodiments of the present invention. Broadly, computer-readable storage media and communications media may be referred to herein as computer-readable media.
In general, the routines executed to implement the embodiments of the invention, may be part of an operating system or a specific application, component, program, module, object, or sequence of instructions. The computer program of the present invention typically is comprised of a multitude of instructions that will be translated by the native computer into a machine-readable format and hence executable instructions. Also, programs are comprised of variables and data structures that either reside locally to the program or are found in memory or on storage devices. In addition, various programs described hereinafter may be identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.
Assets may be further described by associations to other assets.
Data mart schemas may be built using assets stored in data repositories.
The bottom schema is a snowflake schema 302 for a data mart for the “business term” asset type. This schema 302 includes fact table for business terms. Facts stored in the fact table include facts about the business term (such as its name, description, synonyms, and abbreviations). Once again, the dimensions for this fact table are derived from associations of this asset type to other asset types, as shown in
In one embodiment, data marts are dynamically built for groups of related assets that are stored in a variety of data repositories.
As shown in
An overview of an initial load 404 is also shown in
Next, a set of snowflake schemas are derived 408 to represent the assets. Other schemas, such as star schemas, are broadly contemplated and use of such schemas is considered to be embodiments of the invention. Schema elements, including facts, dimensions, and hierarchies, are constructed based on the data stored in the intermediate warehouse 402. In one embodiment, facts may be attributes, simple measures, and complex measures, as noted above. Dimensions are derived from the particular associations of the assets in the data repositories 401. In addition, in one embodiment, the intermediate warehouse schema 402 includes a timestamp to allow versioning of data. The timestamp may be used later to create a time dimension in each data mart 403. Once the snowflake schemas have been created, an initial load is performed to populate the data marts 403 with data from the intermediate data warehouse 402.
After the initial load is complete, embodiments of the invention may be used to incrementally load the intermediate warehouse 402 and data marts 403 with a new version of asset facts and associations that were extracted from the data repositories 401. For example, the incremental load may be triggered by user action, by an event (e.g., monitoring the refresh date of a data repository to discover that an incremental load is needed), or according to a predefined schedule. An overview of an incremental load is also shown in
As shown in
At step 530, the method 500 distinguishes between an initial load and an incremental load scenario. An initial load is a capture of a single first state of the data in the repository into the data warehouse. An incremental load is an update of the data warehouse with a second (i.e., new) state of the data in the repository. For example, a data repository goes to a second state when, at a later point in time following the initial load, some of the data in the data repository has changed or has been newly added.
In the case of an initial load, the method 500 proceeds from step 530 to step 540, at which a set of data marts is built based on the data in the intermediate warehouse. All the data in the warehouse describe some asset, and all the assets may be grouped by their asset type. The method 500 builds data marts for asset types. Put another way, a data mart is built for each respective asset type so that each data mart will describe assets of the same type. The list of data marts may be exhaustive and include one data mart for every asset type in the data repositories. Alternatively, the list of data marts may be limited to only a sub-set of asset types via the user configuration. A snowflake schema for each asset type is constructed based on the associations found in the intermediate data warehouse for the particular asset type. Snowflake schemas for different asset types may have vastly different definitions. A detailed flow illustrating the mechanism of building data marts may be found in
If, however, an incremental load is taking place, the method 500 proceeds from step 530 directly to step 550, at which the new or modified data is added to the existing data marts. At step 550, for each existing data mart, a set of steps are performed to populate it. In one embodiment, the population mechanism is identical regardless of an initial or incremental load scenario. In another embodiment the population mechanism for the incremental load could differ from the population mechanism for the initial load such that only added or modified data is populated with a timestamp. The population mechanism relies on the data mart definition of the respective data mart. A detailed flow illustrating the mechanism of populating the data marts may be found in
In one embodiment of the invention, assets from the data repositories are stored into an intermediate data warehouse implemented as a vertical schema.
An intermediate data warehouse schema exhibits certain properties. According to one embodiment, three properties of an intermediate data warehouse are specified. First, assets may be uniquely identified in the data warehouse. The identity of an asset may be used to derive facts about the asset and to derive associations of the asset to other assets. Facts may be simple measures, which are the base data of an asset, such as a name. Facts may also be complex measures that are derived via computation on the base data of an asset. Second, associations between assets may be direct (asset(a)→asset(b)) or transitive (asset(a)→asset(b)→asset(c)). The set of dimensions for a snowflake schema will be derived from the direct associations of an asset. Hierarchies for the dimensions will be derived for the transitive associations. Third, if a historical view of an asset is desired, then the intermediate data warehouse will associate a timestamp with the facts and associations of the asset.
As shown in
As shown, an ASSET_TYPE table 601 is used to monitor the relevant asset types from the data repositories and based on the user configuration. Every asset type in the table may be used to build a new data mart in which all the facts and dimensions relevant to that asset type will be captured. The NAME field of the ASSET_TYPE table 601 is used as the name for the data mart.
An ASSETS table 602 is used to store the actual information assets. Information assets are of a certain type and are therefore qualified by a type identifier in the ASSET_TYPE table 601. The list of attributes needed to represent an information asset is not fixed. That is, the ASSETS table 602 may include fields like NAME, SHORT_DESC, and so forth.
Information assets may be part of a hierarchy represented through the ASSET_GROUP_MEMBERS table 603. Every asset identified by its ASSET_ID may be the child of another asset identified by the PARENT_ASSET_ID. Both foreign-keys are references to the same ASSET_ID primary-key in the ASSETS table 602. Every such parent-child association may be described by other attributes, e.g., a GROUP_DESC and a HIER_LVL_ID in the ASSET_GROUP_MEMBERS table 603. The HIER_LVL_ID is used to identify the tree level at which the parent-child association exists (i.e., how far below the root level the child lives in the tree).
Information assets may also have associations to other information assets that are not parent-child associations. Those associations are represented via the ASSET_REFERENCES table 604. Once again, two foreign-keys refer back to the ASSETS table 602. Optionally, one may again assign other attributes to these associations, such as to describe or to name the association.
The MEAS_RUN table 605 is used to allow versioning of the records in the intermediate data warehouse. Each information asset, along with all its attributes, measures, and associations, will be assigned a timestamp identified by a unique MEAS_ID. The actual timestamp is stored in attributes such as MEAS_RUN_TMS or MEAS_EXE_TMS. Further, the actual timestamp may represent times such as creation time, update time, or last time we observed an asset. The MEAS_ID is referenced as a foreign-key by tables that include the ASSET_GROUP_MEMBERS table 603 and the ASSET_REFERENCES table 604. This enables the preservation of a complete history of all data relevant to assets. For example, parent-child associations and other associations that once existed will be preserved.
In addition to capturing associations between information assets, facts about information assets are captured. These facts (or measures) again have a type and a value. The type is stored in the MEAS_TYPE table 606 and may have a list of optional attributes to describe or to name the type. A specific measure type is relevant only to a specific information asset type. As shown, the MEAS_TYPE table 606 has a foreign-key association with the ASSET_TYPE table 601.
The actual fact (or measure) is represented as a record in the MEASURES table 607 and uses three references. A measure has a specific type (reference to MEAS_TYPE_ID), is for a specific information asset (reference to ASSET_ID), and is valid at a given time (reference to MEAS_ID). The fact itself may be represented in various formats, such as string, boolean, numeric, etc. Optionally, one may create more fine-grained format representations. For example, one may distinguish between numeric types of integer and double.
In one embodiment of the invention, once the schema for the intermediate data warehouse is defined, an architecture is provided for populating the intermediate data warehouse.
In Figure, a warehouse engine 701 receives a user configuration 703 and populates an intermediate data warehouse 707 using data from data repositories 702. Illustratively, the warehouse engine 701 includes a content selector 704, a content provider 705, and a score computation engine 706.
A control flow 751 exists from a user configuration 703 to the content selector 704. Illustratively, the user configuration 703 is provided to the content selector 704, which determines the acceptable format of the user configuration 703. The content selector 704 receives the configuration and optionally parses it to retrieve relevant elements. In one embodiment of the invention, the configuration at a minimum includes a list of repositories, asset types, associations, and measure elements. Every element has a name and a number of attributes. For example, in the case of an element containing a query attribute, a corresponding value for the query attribute must be provided in the syntax applicable to the data repository API so that the query may be passed directly to the data repository for processing.
A control flow 752 exists from the content selector 704 to the content provider 705. The content provider 705 receives the elements from the content selector 704 and provides data to the score computation engine 706 and the intermediate data warehouse 755. The content provider 705 controls the data in three ways, according to one embodiment. These mechanisms are described in further detail in conjunction with
A control flow 753 exists from the data repositories 702 to the content provider 705. For elements with a query attribute, the content provider 705 issues the query directly to the data repository 702. The user configuration 703 specifies the types of data repositories and the necessary connection information to the data repositories 702.
In the illustrative embodiment, a bidirectional control flow 754 exists between the content provider 705 and the score computation engine 706. Optionally, there may be elements in the user configuration that require processing, i.e., require more than merely querying the data repository. An example is score computations. A score may be either a base score or a composite score. A value for a base score is computed directly from a measure retrieved through the content provider 705 and using an algorithm implemented in the score computation engine 706. A value for a composite score is computed from a list of base scores using an algorithm implemented in the score computation engine 706. Those skilled in the art will recognize, for example, that the architecture 700 could easily be extended to include other processing engines other than a score computation engine 706.
A control flow 755 also exists between the content provider 705 and the intermediate data warehouse 707. Illustratively, data retrieved from the data repositories 702 or computed in the score computation engine 706 is written to the data warehouse 707 by the content provider 705. The content provider 705 terminates when all the elements specified by the content selector 704 have been processed.
Referring now to
At step 830, asset types are provided in the user configuration and are inserted into the warehouse with a name and a uniquely generated ASSET_TYPE_ID in the ASSET_TYPE table 601. Optionally, other attributes may also be inserted into the table. Examples include a query that retrieves all the attributes of an asset of a given type (XQUERY_ATTRIBUTE) and a query that retrieves associations to assets of other asset types (XQUERY_ASSOCIATION).
At step 840, the list of asset types is processed, and for each asset type, a query is executed to retrieve the assets into the ASSETS table 602. Each asset is uniquely identified by its ASSET_TYPE_ID and a generated ASSET_ID. The inserted attributes for an asset are limited to its name (NAME) and a short description (SHORT_DESC) in a preferred embodiment. Additional attributes are processed later as measures in step 890.
At step 850, before the remaining tables are processed, a unique identifier is generated to identify the current execution run. This identifier is called MEAS_ID and is written to MEAS_RUN table 605 in the intermediate data warehouse. The MEAS_ID is later referenced by all remaining tables in the intermediate data warehouse schema. The MEAS_ID provides the timestamp of the current execution run as MEAS_RUN_TMS. The MEAS_ID may be as simple as having a counter set to [max(MEAS_ID)+1] or may encode the current system time in a certain manner. The only requirements for MEAS_ID are for MEAS_ID to be unique and be sorted in ascending order.
Constructing the MEAS_RUN table enables the versioning of records in the intermediate data warehouse, thereby allowing the capture of data changes in the data repositories. Such data includes facts (attributes, measures, complex measures) of an asset as well as the associations of an asset. Illustratively, an asset may be created and thereafter exist in a data repository at one point in time, but may be removed again at a later point in time. Such a change may be captured via the MEAS_ID, which is used to identify the timestamp when data was extracted from the data repository.
At step 860, associations between assets are provided in the user configuration as elements of an asset type. The association element has a query attribute where the query returns the identifier of the asset and the identifier of the referenced asset. An association is a uni-directional association, where the asset of one asset type references an asset of another asset type. Bi-directional associations are represented with two queries in the user configuration: one for asset type A referencing an asset of type B and one for asset type B referencing an asset of type A. Additionally, asset references may also exist between assets of the same type.
At step 870, the asset and the referenced asset already exist in the data warehouse. The association between the asset and the referenced asset is stored as a tuple consisting of ASSET_ID and ASSET_REF in ASSET_REFERENCES table 604. Both identifiers are foreign keys to the ASSETS table 602. In other words, ASSET_ID and ASSET_REF must reference existing assets. All discovered associations are valid with respect to the current measure run and the unique key in the ASSET_REFERENCES table 604 is formed as the triplet: (MEAS_ID, ASSET_ID, ASSET_REF).
At step 875, asset hierarchies are built using a set of recursive queries on the ASSET_REFERENCES table 604. For every asset referenced by the ASSET_ID, the algorithm returns the ASSET_REF and assigns ASSET_REF to be the new ASSET_ID. The recursion stops when no more tuples are returned. Then, the method 800 recursively retraces the found ASSET_REF and ASSET_ID tuples and writes them into the ASSET_GROUP_MEMBERS table 603. The ASSET_REF will be stored as the PARENT_ASSET_ID of the ASSET_GROUP_MEMBERS table 603. In addition, the ASSET_ID will be stored as the ASSET_ID of the ASSET_GROUP_MEMBERS table 603. The HIER_LVL_ID is generated starting with 0 and is incremented for every tuple. Every hierarchy discovered this way is valid with respect to the current measure run. Further, the unique key in the ASSET_GROUP_MEMBERS table 603 is formed as the triplet: (MEAS_ID, ASSET_ID, PARENT_ASSET_ID).
At step 880, measure types that were specified in the user configuration for every asset type are inserted into the warehouse with a name, a unique identifier, and type information for the actual data values expected for the particular measure type. The MEAS_TYPE table 606 is used to store the set of measures for every ASSET_TYPE_ID and to uniquely identify each measure through the ASSET_TYPE_ID and a generated MEAS_TYPE_ID. The mandatory TYPE attribute is used to identify whether the data should be consumed as strings, numerics, or any other data type. Optionally, other attributes may also be inserted into the table. Examples include an attribute representing the maximum length of every data value (LENGTH) and an attribute representing the query used to retrieve the data value (XQUERY).
At step 885, for every simple measure type inserted into the MEAS_TYPE table 606, the method 800 then queries the actual values from the data repository and stores it as a tuple in the MEASURES table 607. The actual value may be a STRING_VALUE, NUMERIC_VALUE, or BOOLEAN_VALUE, based on the data type specified for the particular measure type. The actual value is uniquely identified for a particular measure run, a particular asset, and a particular measure type. Further, the primary key for the MEASURES table 607 is formed as the triplet: (MEAS_ID, ASSET_ID, MEAS_TYPE_ID).
At step 890, for every complex measure type inserted into the MEAS_TYPE table 606, the method 800 computes the measure values using the attributes provided in the user configuration. One attribute identifies the input measure and another attribute identifies the algorithm used to compute the complex measure. At this step, input measure and the algorithm should both already exist for the computation to proceed. In other words, an algorithm is implemented in the score computation engine 706 and the input measure values are available in the MEASURES table 607, where the input measure values have the current MEAS_ID. For a composite complex measure, the method 800 computes the measure value using a list of input measures which include simple measures, complex measures, composite complex measures, or some combination thereof. Once again, the measure value may be computed again with an existing algorithm and an existing set of input values. The result of every computation is stored in the MEASURES table 607 with a unique key consisting of the triplet: (MEAS_TYPE_ID, the MEAS_ID, and the ASSET_ID). After step 890, the method 800 terminates.
In one embodiment of the invention, once the intermediate data warehouse is populated, an architecture is provided for creating and populating data marts.
In
The architecture 900 queries the data in the intermediate data warehouse 901 to generate and populate one or more data marts 909. Each data mart will have a dynamically generated schema, but will have a common structure. An example of a data mart schema may be found in
A control flow 951 exists from the intermediate data warehouse 901 to the schema engine 902. The schema engine 902 is used to define snowflake schemas for the data marts. The schema engine 902 queries the data in the intermediate data warehouse 901 to determine the number, type, and names of data marts to generate. Each data mart 909 is then generated with a single master fact table using the mart generator 903. The definition for the master fact table and the logic to create the master fact table are implemented in the mart generator 903.
A control flow 952 exists from the mart generator 903 and the dimension generator 904. In this flow, a set of dimensions are built for each data mart 909 using the dimension generator 904. The number, types, and names for the dimensions are generated by querying the data in the data warehouse 901, and may vary from data mart to data mart. Three common dimensions are added to every data mart to capture information about time, measures, and attributes. In other embodiments of the invention, however, the common dimension for attributes is optional and may not be included in a data mart.
A control flow 953 exists from the dimension generator 904 to the hierarchy generator 905. In this flow, every dimension constructed by the dimension generator 904 will be assigned a hierarchy using the hierarchy generator 905. The hierarchy for every dimension is also generated by querying the data in the intermediate data warehouse 901. Each hierarchy consists of a set of tables linked together through referential constraints. The number and names of tables vary from dimension to dimension and from data mart to data mart. Finally, the bottom table in a hierarchy is linked to the master fact table. The definition of each table, the logic for creating each table, and the logic for linking the tables together are implemented in the hierarchy generator 905.
A control flow 954 exists from the schema engine 902 to the data marts 909. In this flow, the set of snowflake schemas defined and constructed by the schema engine 902 are persisted into one or more databases. If persisted into a single database, the data marts 909 may be stored in different schemas or namespaces to avoid duplicate name conflicts for tables with common names across multiple snowflake schemas.
A control flow 955 exists from the schema engine 902 to the data engine 906. In this flow, the set of data marts 909 is populated using the data engine 906. Without loss of generality, an assumption may be made that the data marts 909 have not been populated yet and that a full insert is necessary. However, if a data mart has already been populated, the data engine 906 may be used to re-populate or update the data mart, thereby also omitting flow 954 above.
A control flow 956 exists from the intermediate data warehouse 901 to the data engine 906. In this flow, the data engine 906 is used to populate the data marts 909. The data engine 906 queries the data in the intermediate data warehouse 901 and attempts to insert data into all the tables in the data marts 909, including the master fact table and every table in every hierarchy for each dimension of the respective data mart.
A control flow 957 exists from the dimension provider 907 to the fact provider 908. In this flow, the data needed to populate every dimension is obtained from the intermediate data warehouse 901 and queried in the dimension provider 907. By iterating through the list of dimensions and the set of tables in every dimension, the dimension provider 907 populates every table in the hierarchy for every dimension of the respective data mart.
A control flow 958 exists from the data engine 906 to the data marts 909. In this flow, the fact provider 908 queries the intermediate data warehouse 901 to obtain the data for every data mart 909 and populates the master fact table of each data mart 909 with the data. For each data mart 909, the fact provider 908 also populates the foreign key columns used to link the fact table with the dimensions populated in the dimension provider 907. All the data constructed by the dimension provider 907 and by the fact provider 908 is inserted and committed into the data marts 909 generated by the schema engine 902.
As shown, method 1000 begins at step 1010, where the user identifies a list of data marts by asset type. The asset type of each data mart should match a type listed in the ASSET_TYPE table 601. At step 1020, for the list of data marts with an existing type in the ASSET_TYPE table 601, method 1000 iterates through a main loop, identifying a data mart with an asset type identifier. At step 1030 of the main loop, a data mart schema is created for the data mart identified by its asset type identifier. In one embodiment, step 1030 is carried out by the schema engine 902 described above with respect to
At step 1040 of the main loop, the tables are populated with data using the schema defined in step 1030 and the tables created in step 1030. In one embodiment, step 1040 is carried out by the data engine 906 described above with respect to
To aid in the understanding of
A FACT table 1301 (of
A dynamic dimension 1302 (of
A hierarchy of tables 1303 (of
A table USER_DEFINED_TERM_LVL—0_CATEGORY 1304 (of
A FACT_TERM table 1305 (of
Three static dimensions 1306 (of
The ATTRIBUTES_LVL—0_NAME table 1307 (of
Referring now to
At step 1120, the number and type of dimensions varies across data marts. Dynamic dimensions, which have a variable definition, are distinguished from static dimensions, which have a fixed definition. Dynamic dimensions are generated in steps 1120 to 1170. Static dimensions are generated in steps 1180 and 1190. To identify the list of dynamic dimensions for this particular data mart, the method 1100 queries the ASSET_TYPE 601, ASSETS 602, ASSET_GROUP_MEMBERS 603, and ASSET_REFERENCES 604 tables in the intermediate data warehouse. First, the method 1100 lists all assets that are related to or referenced by any asset of type t1 where t1 is the asset type used to identify this particular data mart. Then, the method 1100 extracts a distinct list of all asset types associated to those assets. Finally, t1 itself is added to the distinct list of asset types.
At step 1130, for each dynamic dimension listed in step 1120, the method 1100: (i) generates a hierarchy, (ii) adds a fact table to the hierarchy, and (iii) links the fact table with the master fact table. Because of the nature of the fact tables, the dimension-specific fact tables are referred to as multiple fact tables.
At step 1140, a hierarchy is constructed bottom-up in two steps. In the first step, the bottom (leaf level) of the hierarchy is identified. In the second step, the higher levels (up to the root level) are generated. Alternatively, the hierarchy could also be generated using a top-down approach. Either approach requires a recursive algorithm to generate the variable number of levels between the leaf level and the root level of the hierarchy.
To generate the leaf level of the hierarchy, the method 1100 queries the ASSET_GROUP_MEMBERS table 603 to find an asset that is a candidate for the lowest level of the hierarchy. The asset is of the same type as the dimension and has the highest possible value for its level identifier. Using the chosen candidate, a leaf level table is generated that is identified by the type of the dimension and the level of the candidate. The list of attributes for this table is again fixed and identical throughout all levels of a hierarchy so that the hierarchy may be consumed more easily by downstream applications. The table includes at least one primary key to uniquely identify the asset and one foreign key to identify a parent asset in the next level table.
After the leaf level table has been created, a recursive algorithm generates the remaining tables up to the root level of the hierarchy. The parent-child associations captured in the ASSET_GROUP_MEMBERS table 603 are traversed beginning with the candidate asset up to the parent asset that has a level identifier of 0 and no further parent. For every step in the recursion, a table is generated that is again identified by the name of the dimension and the level identifier. The table is linked to the underlying table in the hierarchy using a primary-key/foreign-key reference between the asset id column and the parent asset id column.
At step 1150, the hierarchy is completed by adding a multiple fact table as a link between the hierarchy and the master fact table. The multiple fact table has a fixed list of attributes but should contain at least: (i) one foreign key to the unique asset identifier in the leaf table of the hierarchy and (ii) one foreign key to the unique asset identifier in the master fact table. The multiple fact table itself is identified only by the name of the dimension.
At step 1160, the multiple fact table is linked with: (i) the master fact table and (ii) with the leaf level table of the hierarchy by means of the two foreign keys created in the multiple fact table.
At step 1170, if there are more dynamic dimensions to be processed as identified in the list created in 1120, the method 1100 loops back to step 1130.
At step 1180, after all dynamic dimensions have been processed, three static dimensions are generated. These three static dimensions capture information about time, measure types, and attributes. Each static dimension has a simple hierarchy consisting of only one table. Further, each static dimension does not require a multiple fact table. The time and measures dimension tables have a fixed (but not necessarily the same) list of attributes. A primary key may be used to link the static dimensions with the master fact table.
In other embodiments of the invention, however, the static dimension representing attributes is optional. Attributes of an asset are values of type string, boolean, or timestamp, which may not be aggregated. Depending on the consuming downstream applications, the values may or may not be needed in the form of a de-normalized table to be directly consumed by querying the columns of the de-normalized table. The attributes dimension is the dimension that provides a flat table with columns for every attribute of a non-numeric type. If the consuming application is able to treat attributes in the same way as measures, then the static dimension representing attributes is not needed.
If the static dimension representing attributes is needed, an attributes dimension table is generated that has a list of dynamically constructed attributes. To generate the attributes dimension table, the method 1100 queries the MEAS_TYPE table 606 in the intermediate data warehouse and extracts all measure types that are not numeric, creating one column for each. A unique key column is added to link the attributes dimension with the master fact table.
At step 1190, the two (or three) static dimensions are linked with the master fact table using the foreign keys created in the master fact table and the primary keys created in the static dimension tables. After step 1190, after all tables have been generated, the method 1100 terminates.
Referring now to
To populate the master fact table, method 1200 queries the ASSET_TYPE 601, ASSETS 602, MEASURE_RUN 605, MEASURE_TYPE 606, and MEASURES 607 tables to retrieve every measure value for every measure type, for every asset with an asset type that matches the particular data mart. Optionally, method 1200 may only retrieve these values for a specific timestamp to update a data mart, or retrieve the entire data set to populate a new data mart.
At step 1220, a list of dynamic dimensions is identified. In accordance with the data mart structure created in the schema engine 902 of
At step 1230, a main loop populates a dynamic dimension in each iteration. Static dimensions are populated later in step 1290. Every dynamic dimension has exactly one dynamically generated hierarchy associated with it. The hierarchy includes a set of tables. Each table has an identifier that associates the table with the dimension. At step 1240, a list of tables for the hierarchy is identified. The list of tables for the hierarchy may either be extracted from the schema engine model or computed with the logic found in the dimension generator 904.
At step 1250, the list of tables in a dynamic dimension hierarchy is processed top-down beginning with the root level table. At step 1260, all tables within a dynamic dimension hierarchy are populated using the same logic. Method 1200 queries the ASSET_TYPES 601, ASSETS 602, and ASSET_GROUP_MEMBERS 603 tables to extract all asset identifiers and parent asset identifiers for every asset (i) that is of the same type as the dimension; (ii) that is the same level as the table; and (iii) that has parent asset identifier already populated into the table above in the hierarchy. For the root level table, only the type of the dimension should match and the level should be zero. The data is queried from the intermediate data warehouse and directly inserted into the data mart table either through insert-select statements or any other means of data extract and load. Besides the asset identifier and parent asset identifier, method 1200 extracts all those attributes that describe the asset in the ASSETS table 601 and that may be populated into the mart table, e.g., asset name, asset description, etc.
Hierarchies are used to store data sets that may be represented as trees. There are three forms of trees and three matching forms of hierarchies. Trees may be either be balanced (all leaf nodes are at the same level), unbalanced (leaf nodes are not all at the same level, but there are no holes between the nodes), or ragged (all nodes are at the same level but there are holes between the nodes). The hierarchy generator 905, however, only links the leaf level table with the multiple fact table in the data mart schema. Such a linking mechanism only supports balanced hierarchies. In order to support unbalanced and ragged tree representations, unbalanced and ragged tree representations must be converted into balanced hierarchies in the following ways.
For a balanced tree representation, only those assets that have the exact same level as the table within the hierarchy (as described above) should be extracted. For an unbalanced tree representation, all assets are extracted that have the same or lower level identifier as the current table in the hierarchy; the requirement is that the parent asset identifier exists in the above table in the hierarchy. In addition, every leaf node in the tree must be carried forward to the leaf level table in the hierarchy. This may be done by copying assets that have no more children from higher level tables to lower level tables until the leaf level table is reached. For a ragged tree representation, logic similar to the logic for unbalanced trees is used. Holes in the tree representation will be automatically removed because lower level assets are allowed to be stored in a higher level table in the hierarchy. These holes are virtually shifted below the leaves in the tree. The holes are closed in the hierarchy by copying nodes with no children.
At step 1270, the method 1200 repeats steps 1250 and 1260 until no more tables exist in the hierarchy and the leaf table is reached. At step 1280, to associate the facts stored in the master fact table with the data stored in the hierarchies, a table is used that links the identifiers found in the master fact table with the identifiers found in the dimensions. Such a table is referred to as a multiple fact table. A multiple fact table merely references the facts with the appropriate dimension and does not contain any data itself. To make the association time sensitive, a time identifier is added. The query used to populate each multiple fact table reads from the ASSET_TYPE 601, ASSETS 602, and ASSET_REFERENCES 604 tables to obtain all the asset identifiers used in the fact table and to map them to the asset identifier used in the dimension. The asset identifier in the fact table is of the same type as the data mart, whereas the asset identifier used in the dimension will match the type of the dimension. The ASSET_REFERENCES table 604 contains all the associations regardless of the asset type. The query is constructed using filters on asset types. Further, the timestamp is retrieved representing the time at which the association was valid. There may be cases where an asset identifier found in a dimension has no association to any asset identifier found in the fact table. Such “orphaned” assets may either be ignored or be grouped and associated with a dummy fact group.
At step 1285, the method 1200 repeats steps 1230 through 1280 until all dynamic dimensions have been processed. At step 1290, the remaining three dimensions to be populated are static dimensions for storing information about time, measure types, and string attributes.
To populate the static dimension for time, the method 1200 proceeds as follows. First, the timestamps for every measure for every asset of every type are available in the MEAS_RUN table 605. Method 1200 queries this table and joins it with the ASSET_TYPE 601 and ASSETS 602 tables to filter only those timestamps that are needed for any measure for any asset that has the same type as the data mart. Different timestamps that represent different events (e.g., asset creation, population, update) may also be populate into the same time dimension provided different identifiers are used for the different timestamps.
To populate the static dimension for measure types, the method 1200 proceeds as follows. First, the values stored in the master fact table are measures of different types. The measure type dimension identifies the type of these measures. Every asset type has a list of relevant measure types. The method 1200 queries the ASSET_TYPE 601 and MEASURE_TYPE 602 tables in the intermediate data warehouse to obtain measure types relevant to our type of data mart.
To populate the optional static dimension for attributes, the method 1200 proceeds as follows. First, if the schema engine 902 generates a static dimension for attributes in step 1180, then the static dimension for attributes is populated at this step. The static dimension for attributes is only required if a consuming downstream application requires it. Instead of a normalized representation of facts as measures of a specific type (as done above with the measure types dimension), a de-normalized representation for attributes is instead used. The attributes dimension has one column for every attribute type. Further, the values of the columns are directly stored in the cells of the columns. A nested loop is used to populate the cells. In the outer loop, method 1200 queries the ASSET_TYPE 601, ASSETS 602, MEASURE_RUN 605, MEASURE_TYPE 606, and MEASURES 607 tables in the same manner as in step 885. In the inner loop, method 1200 processes the results of the query and inserts the data into the proper column as identified by the measure type. Alternatively, method 1200 may query the master fact table directly and insert the data into the attributes table. After step 1290, once all tables have been populated, the method 1200 terminates.
To demonstrate the dynamic construction of marts, dimensions, and hierarchies, a small data sample is extracted from the example shown in
To further demonstrate the dynamic construction of marts, dimensions, and hierarchies,
The ASSET_TYPE “Category” is highlighted bold and shall be the asset type used to generate a data mart in
To further demonstrate the dynamic construction of marts, dimensions, and hierarchies, based on the sample data warehouse schema shown in
The dynamic dimensions have hierarchies with one level for the ‘USER’ dimension and two levels for the “USER_DEFINED” and “PHYSICAL_LAYOUT” dimensions, respectively. Data items are (i) populated into the appropriate level within the correct dimension and (ii) linked together using the unique identifier.
There is one master fact table 1611 containing all four unique identifiers for the four categories found in the sample data. Additionally, three multiple-fact tables 1615-1617 are generated and populated to link the hierarchies in the dynamic dimensions with the master fact table.
Of course, the embodiments described herein are intended to be illustrative and not limiting of the invention, and other embodiments are broadly contemplated. Those skilled in the art will recognize, for example, that data mart schemas other than a snowflake schema, such as a star schema, may be supported by embodiments of the invention. Moreover, association information between assets may be found in a data repository, specified in a user configuration, or both. Furthermore, the static dimension for attributes may be optional in some embodiments of the invention where downstream applications do not require the static dimension for attributes. Further still, the static dimension for time may be optional in some embodiments of the invention where a historical view of data is not required. In addition, the data repositories may be of any type, such as relational, object, or object-relational.
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6167405 | Rosensteel et al. | Dec 2000 | A |
| 6212524 | Weissman et al. | Apr 2001 | B1 |
| 6385604 | Bakalash et al. | May 2002 | B1 |
| 6651062 | Ghannam et al. | Nov 2003 | B2 |
| 6721749 | Najm et al. | Apr 2004 | B1 |
| 7117215 | Kanchwalla et al. | Oct 2006 | B1 |
| 7313561 | Lo et al. | Dec 2007 | B2 |
| 7315849 | Bakalash et al. | Jan 2008 | B2 |
| 7319996 | Chen et al. | Jan 2008 | B2 |
| 7333982 | Bakalash et al. | Feb 2008 | B2 |
| 7392248 | Bakalash et al. | Jun 2008 | B2 |
| 7680828 | Gorelik | Mar 2010 | B2 |
| 7730057 | Bell et al. | Jun 2010 | B2 |
| 20040181440 | Yeh et al. | Sep 2004 | A1 |
| 20060031250 | Henigman et al. | Feb 2006 | A1 |
| 20060117057 | Legault et al. | Jun 2006 | A1 |
| 20060259507 | Higuchi | Nov 2006 | A1 |
| 20060271568 | Balkir et al. | Nov 2006 | A1 |
| 20070185867 | Maga et al. | Aug 2007 | A1 |
| 20070250524 | Le | Oct 2007 | A1 |
| 20070294208 | Chowdhary et al. | Dec 2007 | A1 |
| 20080021893 | Bakalash et al. | Jan 2008 | A1 |
| 20080021915 | Bakalash et al. | Jan 2008 | A1 |
| 20080027970 | Zhuge et al. | Jan 2008 | A1 |
| 20080104089 | Pragada et al. | May 2008 | A1 |
| 20090012816 | Cookson et al. | Jan 2009 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20100106747 A1 | Apr 2010 | US |
