Virtual data warehousing
View Patent ↗A virtual data warehouse (the functional equivalent of a conventional data warehouse) that provides aggregated views of the complete data inventory. The virtual data warehouse contains metadata, which is used to form a logical enterprise data model that is part of the database of record (DBOR) infrastructure. Each legacy back-end database system is published on the infrastructure, with its metadata extracted and used as noted above. The infrastructure software uses standard J2EE, JMS and reusable EJBs, for transactional unit requests, and ETL (extract-transform-load) tools for real-time bulk loading of data.
1. An arrangement for providing information to a plurality of different client views within an enterprise without creating an actual data warehouse, the arrangement comprising
a virtual data warehouse including
a plurality of disparate back-end database systems associated with a common enterprise, each back-end database system capable of having a different legacy architecture and organization;
a database of record (DBOR) infrastructure for storing in a single physical location a plurality of metadata extracted from each back-end database system of the plurality of disparate back-end database systems so as to form a logical enterprise data module, the logical enterprise data module responsive to information requests from the plurality of different client views.
2. The arrangement as defined in claim 1 wherein the DBOR infrastructure further comprises extract-transform-load (ETL) tools for providing connection to the plurality of disparate back-end database systems.
3. The arrangement as defined in claim 1 wherein the DBOR infrastructure is dynamic and is further utilized to generates an updated logical enterprise data module as new database systems are published on the infrastructure.
4. The arrangement as defined in claim 3 wherein the metadata associated with newly published database systems is extracted and used to update the local enterprise data module within the DBOR infrastructure.
5. The arrangement as defined in claim 1 wherein the plurality of different client views includes at least one of the following views: customer, financial, data entity and data metrics.
6. The arrangement as defined in claim 5 wherein the plurality of different client views further includes at least one of the following view: product, service, network.
7. The arrangement as defined in claim 1 wherein the plurality of disparate back-end database systems are physically disparate.
8. The arrangement as defined in claim 1 wherein the plurality of disparate back-end database systems are organizationally disparate.
9. The arrangement as defined in claim 1 wherein the plurality of disparate back-end database systems are both physically and organizationally disparate.