Pre-Grant Publication Number: 20070124317
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer-to-Patent forwards the Top 10 most relevant prior art submissions and their annotations to the United States Patent and Trademark Office.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | Patent by D2K Inc. regarding a method for immediate delivery of data warehouse and/or data mart information for optimum decision support. |
Basic Information
| Type of Prior Art | Issued Patents - US |
| Country | United States of America |
| Patent/Application # | 5781911 |
| Kind Code | United States (US) - United STATES Patent - A |
| Patentee Name | D2K, Incorporated |
| Relevant Pages, Columns, or Lines | Claim1 and Claim 8 |
| URL | http://www.google.com/patents?i... |
| Filing Date | July 14, 1998 |
| Additional Information | |
Notes / To Do
| Notes | |
Excerpt
Excerpt Claim:
1. An integrated system of data warehousing and data delivery comprising:
a supplier module for a user to define an extraction order comprising a first tasklist of what data are to be extracted from one or more existing data processing systems, what transformations are to be performed and into what one or more databases said extracted and transformed data are to be stored, and a set of timings of when said first tasklist is to be executed;
a publisher module for a user to define s publisher order comprising a second tasklist of which of said extracted and transformed data we to be published, what transformations are to be performed on the published data and into what one or more databases said published data are to be stored, and a set of timings of when said second tasklist is to be executed;
a subscriber module for a user to define a subscription order comprising a third tasklist of which of said published data are to be retrieved, what transformations are to be performed on the retrieved data and the destinations the retrieved data are to be delivered, and a set of timings of when said third tasklist is to be executed;
a master scheduler module for scheduling said extraction orders said publisher order and said subscription order to produce a master schedule of when these orders are to be executed and in what sequence;
a concurrent manager module for managing the concurrent execution of said extraction order, said publisher order and said subscription order according to said master schedule;
a transport service module for transporting data from said one or more existing data processing systems to said databases of said extracted and transformed data, from said databases of said extracted and transformed data to said databases of said published data, and from said databases of said published data to the destinations specified in said subscription order; and
a transformation service module for transforming data according to specifications defined by a user using one or more of said supplier module, said publisher module and, said subscriber module.
8. A method of data warehousing and data delivery as in claim 6 wherein one or more of said extraction order, said published order and said subscription order further comprises a dependency list that contains a set of events to trigger the execution of one or more of said extraction order, publisher and subscription order. |
Relevance
Claims
1
A method for managing data in an operational datastore and a staging datastore comprising:
configuring the staging datastore, comprising:
(a) defining a relationship between one or more fields of a first data structure in the staging datastore and one or more fields of a second data structure in the operational datastore, wherein the first data structure is a data source for the second data structure in the operational datastore; and
(b) defining a first query comprising at least one field in the first data structure on which the relationship between the data structures is defined, the first query being configured to query and retrieve data from the first data structure;
periodically migrating data from the first data structure to the second data structure according to the defined relationship, wherein the migrating occurs in response to a predefined condition being met;
receiving a user defined query configured to query and return data from the operational datastore;
in response to receiving the user defined query, executing the first query to retrieve, from the first data structure, any non-migrated data relevant to the user defined query;
in the event any non-migrated data relevant to the user defined query are returned, transforming the returned non-migrated data into a format consistent with the format of the second data structure;
executing the user defined query against a data set including the second data structure and the transformed data; and
returning results for the executed user defined query.
Relevance
See Figure 2 of the attached pdf file, complete copy this prior art. Also see page 7 of the attached pdf file in the Detailed Description section where the document describes "a transport of data from a Data Source to a Staging Area, from a Staging Area to a Data Warehouse or Data Mart, or from a Data Warehouse or DataMart to a destination specified by a subscriber" (page 7,column 3, section 30) as well as a description of a task list that contains "...tasks for transporting the transformed data into a Staging Area." (page 7, column 3, section 60). The Data Warehouse or Data Mart in this case can be seen as the operational data store upon which decisions are usually based for a business so there is a description of transporting data from a Staging Area to and Operational Area.
See Figure 2 of the attached pdf file, complete copy this prior art. Also see page 7 of the attached pdf file in the Detailed Description section where the document describes "a transport of data from a Data Source to a Staging Area, from a Staging Area to a Data Warehouse or Data Mart, or from a Data Warehouse or DataMart to a destination specified by a subscriber" (page 7,column 3, section 30) as well as a description of a task list that contains "...tasks for transporting the transformed data into a Staging Area." (page 7, column 3, section 60). The Data Warehouse or Data Mart in this case can be seen as the operational data store upon which decisions are usually based for a business so there is a description of transporting data from a Staging Area to and Operational Area.
Claim Chart
All
5
The method of Claim 1, wherein retrieving non-migrated data relevant to the user defined query from the staging datastore comprises:
selecting the first query from a plurality of predefined queries, wherein the plurality of predefined queries are based on other predefined relationships between the other data structures in the operational datastore and staging datastore, respectively; and
executing the selected query.
Relevance
predefined queries are no more than predefined triggers for future action based on predefined relationships in the data structures of the operational datastore and staging datastore
predefined queries are no more than predefined triggers for future action based on predefined relationships in the data structures of the operational datastore and staging datastore
Claim Chart
All
12
The system of Claim 11, wherein the operational datastore, to determine the presence of non-migrated data in the staging datastore, is further configured to examine a tracking data structure in the operational datastore, wherein the tracking data structure contains data indicating the presence of non-migrated data in the staging datastore.
Relevance
the tracking data structure is a dependency list
the tracking data structure is a dependency list
Claim Chart
All
