IP Library › Granted Patent US 12,361,005
Granted Patent B2
US 12,361,005 · App. 18/647,590 · Granted Jul 15, 2025

ETL-less zero-redundancy system and method for reporting OLTP data

Inventors: Hasso Plattner (Schriesheim, DE); Anja Bog (Potsdam, DE); Jan Schaffner (Berlin, DE); Jens Krueger (Berlin, DE); Alexander Zeier (Berlin, DE)
Assignee: SAP SE
G06F16/2455G06F16/221G06F16/2379G06F16/27G06F16/283G06F16/284G06F16/278
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,361,005
App. No.
18/647,590
Granted
Jul 15, 2025
Kind
B2
Abstract

A system includes a relational database management system component and a column-oriented data processing component. The relational database system component stores database information in a row format. The column-oriented data processing component stores the database information in a column format. In response to a database update request, the relational database management system component updates the database information stored in the row format; the relational database management system component notifies the column-oriented data processing component of the database update request; and the column-oriented data processing component updates the database information stored in the column format. In response to a query request, the column-oriented data processing component generates a query response based on the database information stored in the column format. In this manner, the system is able to generate up-to-date reports without the need for extraction, translation and loading procedures.

Claims (54)

1. A computer-implemented method of processing database information for both transacting and reporting, comprising the steps of:

storing, by a computer system that includes a processor and a memory, said database information in a row format;

storing, by said computer system, said database information in a column format;

in response to a database update request, updating said database information stored in said row format;

in response to said database update request, updating said database information stored in said column format, wherein said database information stored in said row format and said database information stored in said column format are updated concurrently and share a consistent view of said database information; and

in response to a query request to retrieve data, generating a query response based on said database information stored in said column format, wherein generating said query response accesses only one or more columns needed directly for generating said query response.

2. The computer-implemented method of claim 1 , wherein storing said database information in said row format comprises storing said database information in said row format using a relational database management system; and

wherein storing said database information in said column format comprises storing said database information in said column format using a column-oriented data processing system.

3. The computer-implemented method of claim 2 , wherein said column-oriented data processing system comprises a main index and a delta index, wherein said main index is configured to store main data corresponding to said database information, said method further comprising:

receiving said database update request;

updating, by said relational database management system in response to said database update request, said database information stored in said row format;

notifying, by said relational database management system, said column-oriented data processing system of said database update request using a delta updates access; and

controlling, by said column-oriented data processing system, said delta index to store delta data according to said delta updates access, wherein said delta data corresponds to a plurality of updated database information.

4. The computer-implemented method of claim 2 , said method further comprising:

receiving said database update request;

updating, by said relational database management system in response to said database update request, said database information stored in said row format;

notifying, by said relational database management system, said column-oriented data processing system of said database update request; and

updating, by said column-oriented data processing system, said database information stored in said column format.

5. The computer-implemented method of claim 2 , said method further comprising:

receiving said query request; and

generating, by said column-oriented data processing system in response to said query request, said query response based on said database information stored in said column format.

6. The computer-implemented method of claim 1 , wherein said computer system stores said database information in said column format using compression.

7. The computer-implemented method of claim 1 , wherein said computer system stores said database information using both vertical fragmentation and horizontal fragmentation.

8. The computer-implemented method of claim 1 , wherein each column is stored by itself.

9. The computer-implemented method of claim 1 , wherein said one or more columns needed directly for generating said query response is not all of said columns.

10. The computer-implemented method of claim 1 , wherein said computer system stores said database information in said column format using vertical fragmentation across a plurality of networked computers.

11. A computer system storing a computer program for processing database information for both transacting and reporting, said computer program being executed by said computer system, said computer system comprising:

a processor; and

a memory storing said computer program, wherein said computer program, when executed by said processor, controls said computer system to perform a method including:

storing said database information in a row format,

storing said database information in a column format,

in response to a database update request, updating said database information stored in said row format,

in response to said database update request, updating said database information stored in said column format, wherein said database information stored in said row format and said database information stored in said column format are updated concurrently and share a consistent view of said database information, and

in response to a query request to retrieve data, generating a query response based on said database information stored in said column format, wherein generating said query response accesses only one or more columns needed directly for generating said query response.

12. The computer system of claim 11 , wherein said computer program, when executed by said processor, controls said computer system to perform the method further comprising:

mapping an on-line analytical processing query into an aggregation call; and

sending said aggregation call as said query request.

13. The computer system of claim 11 , wherein said database information stored in said row format and said database information stored in said column format are stored in a main memory of said computer system.

14. The computer system of claim 11 , wherein a column-oriented data processing component is configured to store said database information in said column format, wherein said column-oriented data processing component comprises:

a monitoring component, wherein said monitoring component is configured to merge delta data into main data according to a criterion.

15. The computer system of claim 11 , wherein a relational database management system component is configured to store said database information in said row format, wherein said relational database management system component comprises:

a plurality of database tables;

a queue of index objects; and

a kernel, wherein said kernel is configured to manage the plurality of database tables, wherein said kernel is configured to manage the queue of index objects, and wherein said kernel is configured to interact with a file system.

16. The computer system of claim 11 , wherein a relational database management system component is configured to store said database information in said row format, wherein a column-oriented data processing component is configured to store said database information in said column format, and wherein said relational database management system component is configured to communicate with said column-oriented data processing component via a delta updates access.

17. The computer system of claim 11 , wherein a relational database management system component is configured to store said database information in said row format, wherein a column-oriented data processing component is configured to store said database information in said column format, and wherein said column-oriented data processing component is configured to communicate with said relational database management system component via a persist data access.

18. The computer system of claim 11 , wherein said database information stored in said row format and said database information stored in said column format are a same data.

19. The computer system of claim 11 , wherein said database information includes a plurality of columns, wherein a column-oriented data processing component is configured to store said database information in said column format, and wherein said column-oriented data processing component is configured to store each of said plurality of columns as a plurality of tables, respectively, with a plurality of surrogate identifiers duplicated in each of said plurality of tables.

20. A computer program embodied on a non-transitory computer-readable medium and implemented by a computer system for processing database information for both transacting and reporting, wherein said computer system includes a processor and a memory, said computer program being executed by said processor and controlling said computer system to perform a method comprising:

storing, by said computer system, said database information in a row format;

storing, by said computer system, said database information in a column format;

in response to a database update request, updating said database information stored in said row format;

in response to said database update request, updating said database information stored in said column format, wherein said database information stored in said row format and said database information stored in said column format are updated concurrently and share a consistent view of said database information; and

in response to a query request to retrieve data, generating a query response based on said database information stored in said column format, wherein generating said query response accesses only one or more columns needed directly for generating said query response.

Continuity (6)
Continuation 17893916 · Aug 23, 2022
Continuation 16867377 · May 5, 2020
Continuation 15424639 · Feb 3, 2017
Continuation 12234497 · Sep 19, 2008
Provisional Application 60994893 · Sep 21, 2007
Related Publication 20240354300A1 · Oct 24, 2024
References Cited (142)
US 5625815A · Maier et al. · 1997 [cited by applicant]
US 5649089A · Kilner · 1997 [cited by applicant]
US 5794229A · French et al. · 1998 [cited by applicant]
US 5794241A · Loaiza · 1998 [cited by applicant]
US 6006216A · Griffin et al. · 1999 [cited by applicant]
US 6374263B1 · Bunger et al. · 2002 [cited by applicant]
US 6477536B1 · Pasumansky et al. · 2002 [cited by applicant]
US 6901380B1 · Bremers · 2005 [cited by applicant]
US 6980980B1 · Yeh · 2005 [cited by applicant]
US 7024414B2 · Sah et al. · 2006 [cited by applicant]
US 7236974B2 · Bhattacharjee et al. · 2007 [cited by applicant]
US 7480663B2 · Colossi et al. · 2009 [cited by applicant]
US 20030187884A1 · Holenstein et al. · 2003 [cited by applicant]
US 20040010502A1 · Bomfim et al. · 2004 [cited by applicant]
US 20040030703A1 · Bourbonnais et al. · 2004 [cited by applicant]
US 20040054922A1 · Hiraga et al. · 2004 [cited by applicant]
US 20040205066A1 · Bhattacharjee et al. · 2004 [cited by applicant]
US 20050076036A1 · Le · 2005 [cited by applicant]
US 20050187977A1 · Frost · 2005 [cited by applicant]
US 20050262118A1 · Witt · 2005 [cited by applicant]
US 20060004686A1 · Molnar et al. · 2006 [cited by applicant]
US 20060004691A1 · Sifry · 2006 [cited by applicant]
US 20060206507A1 · Dahbour · 2006 [cited by applicant]
US 20060271504A1 · Anderson et al. · 2006 [cited by applicant]
US 20070208753A1 · Mitchell et al. · 2007 [cited by applicant]
US 20070255763A1 · Beyerle et al. · 2007 [cited by applicant]
US 20080046400A1 · Shi et al. · 2008 [cited by applicant]
US 20080059492A1 · Tarin · 2008 [cited by applicant]
US 20080281784A1 · Zane et al. · 2008 [cited by applicant]
US 20090006331A1 · Fuxman et al. · 2009 [cited by applicant]
AU 2008300503B2 · 2013 [cited by applicant]
CA 2425033A1 · 2004 [cited by applicant]
IN 1532CHENP2010 · 2010 [cited by applicant]
JP 2004530213A · 2004 [cited by applicant]
JP 2004303212A · 2004 [cited by applicant]
JP 2005018751A · 2005 [cited by applicant]
JP 2006155663A · 2006 [cited by applicant]
JP 2007334402A · 2007 [cited by applicant]
JP 5421269B2 · 2014 [cited by applicant]
WO 2005098652A2 · 2005 [cited by applicant]
WO 2006060773A2 · 2006 [cited by applicant]
WO 2006136025A1 · 2006 [cited by applicant]
Office Action mailed Oct. 17, 2011 for Chinese Patent Application No. 200880108120.6 entitled “ETL-less Zero Redundancy System and Method for Reporting OLTP Data”. [cited by applicant]
Examiner's first report for Australian Patent Application No. 2008300503 dated May 22, 2012. [cited by applicant]
Second examination report for Chinese Patent Application No. 200880108120.6 mailed May 2, 2012. [cited by applicant]
First Examination Report in corresponding Canadian Patent Application No. CA 2,700,074, mailed Jun. 19, 2014; 2 pages. [cited by applicant]
Notification of Third Office Action in corresponding China Patent Application No. CN 200880108120.6, mailed Jan. 14, 2013; 8 pages. [cited by applicant]
Notification of Fourth Office Action in corresponding China Patent Application No. CN 200880108120.6, mailed Sep. 22, 2013; 8 pages. [cited by applicant]
Notice of Issuance in corresponding China Patent Application No. CN 200880108120.6, mailed Jun. 5, 2014; 2 pages. [cited by applicant]
Mike Stonebraker, et al.; “C-Store: A Column-oriented DBMS”; from Proceedings of the 31st VLDB Conference, Trondheim, Norway; 2005; 12 pages. [cited by applicant]
Extended European Search Report in corresponding European Patent Application No. EP 07117089.8, mailed Jan. 18, 2008; 6 pages. [cited by applicant]
First Examination Report in corresponding European Patent Application No. EP 07117089.8, mailed Dec. 14, 2012; 5 pages. [cited by applicant]
Masayuki Unoki: A new product “Sybase IQ” that realizes an interactive data warehouse, Business Communication, Japan, Business Communications Co., Jul. 1, 1996, vol. 33, No. 7. pp. 19-24. [cited by applicant]
Translation of JP Examination Report for JP Appln. No. 2010-525373 dated Feb. 26, 2013, 5 pages. [cited by applicant]
Ramamurthy et al., “A Case for Fractured Mirrors,” VLDB Journal, 12(2), 89-101, 2003, 12 pages. [cited by applicant]
The TimesTen Team, “In-Memory Data Management for Consumer Transactions: The TimesTen Approach,” Proceedings of the 1999 Acm Sigmod International Conference on Management of Data, ACM,, Jun. 1999, 2 pages. [cited by applicant]
Invalidity Contentions [including U.S. Pat. No. 9,626,421], Case No. 3:18-cv-03670-WHO, United States District Court, Northern District of California, Oct. 31, 2019, 28 pages. [cited by applicant]
Invalidity Contentions, Exhibit A-1, Case No. 3:18-cv-03670-WHO, United States District Court, Northern District of California, Molnar applied to the '421 Patent, Oct. 31, 2019, 144 pages. [cited by applicant]
Invalidity Contentions, Exhibit A-2, Case No. 3:18-cv-03670-WHO, United States District Court, Northern District of California, Zane applied to the '421 Patent, Oct. 31, 2019, 56 pages. [cited by applicant]
Invalidity Contentions, Exhibit A-3, Case No. 3:18-cv-03670-WHO, United States District Court, Northern District of California, Ramamurthy applied to the '421 Patent, Oct. 31, 2019, 69 pages. [cited by applicant]
Date, “An Introduction to Database Systems”, 8th Edition, 2004, 161 pages. [cited by applicant]
Date, “Database in Depth Relational Theory For Practitioners” 1st Edition, 2005, 228 pages. [cited by applicant]
Gray et al., “Data Cube A Relational Aggregation Operator”, IEEE 1996, pp. 152-159. [cited by applicant]
Gray et al. “Transaction Processing Concepts and Techniques”, 1993, pp. 375-492. [cited by applicant]
Managing MaxDB SPC1150 Version 7.6, 2006, 106 pages. [cited by applicant]
MaxDB Database Administration Version 7.7, 2007, 206 pages. [cited by applicant]
Mcdonald et al., “Mastering the SAP Business Information Warehouse”, 2nd Edition, 209 pgs. [cited by applicant]
Microsoft Computer Dictionary, 5th Edition, 18 pages. [cited by applicant]
Ritchie “Relational Database Principles”, 2nd Edition, 2002, 107 pages. [cited by applicant]
Thesing, MaxDB 7.6 Performance Analysis, 2007, 65 pages. [cited by applicant]
TREX-SAP NetWeaver 2004 Installation Guide, 79 pages. [cited by applicant]
TREX-SAP Netweaver's Search and Classification Engine, Jul. 2008, 48 pages. [cited by applicant]
Upgrade Guide From TREX 6.1 To SAP NetWeaver 2004s TREX, Dec. 2005, 34 pages. [cited by applicant]
Wikipedia “Column-Oriented DBMS”, Nov. 2007, 3 pages. [cited by applicant]
Wikipedia “Comparison of RDBMSs”, Oct. 2006, 5 pages. [cited by applicant]
Wikipedia “List of RDBMSs”, Oct. 2006, 3 pages. [cited by applicant]
Wikipedia “MaxDB”, Feb. 2006, 4 pages. [cited by applicant]
Wikipedia “Relational Database”, Oct. 2006, 5 pages. [cited by applicant]
Zhang “Adapting OLAP Analysis To The User's Interest Through Virtual Cubes”, 2006, 10 pages. [cited by applicant]
Teradata Proposed Claim Terms for Construction, Nov. 14, 2019, 10 pages. [cited by applicant]
Corrected SAP Proposed Claim Terms for Construction, Nov. 15, 2019, 4 pages. [cited by applicant]
SAPs Constructions and Evidence, Dec. 5, 2019, 2 pages. [cited by applicant]
Joint Claim Construction Statement, Exhibit 3 Filed Dec. 30, 2019, 130 pages. [cited by applicant]
Joint Claim Construction And PreHearing Statement, Filed on Dec. 30, 2019, 66 pages. [cited by applicant]
Wikipedia “Max DB”, Sep. 2007, 4 pages. [cited by applicant]
Declaration of David Maier in Support of SAP's Markman Brief, dated Feb. 5, 2020, 42 pages. [cited by applicant]
W.H. Inmon. Information Management: World-Class Business Intelligence. DM Review Magazine, Feb. 2005. [cited by applicant]
Wikipedia “Column-Oriented DBMS”, Sep. 2006, 1 pages. [cited by applicant]
Wikipedia “RDBMS”, Oct. 2006, 3 pages. [cited by applicant]
Exhibit 3, Claim Construction Chart-Final, 66 pages. [cited by applicant]
Preliminary Claim Construction and Extrinsic Evidence, Dec. 5, 2019, 49 pages. [cited by applicant]
SAP SE's Opening Claim Construction Brief, dated Feb. 13, 2020, 31 pages. [cited by applicant]
European Search Report (from a corresponding foreign application), U.S. Appl. No. 07/117,089, mailed Jan. 8, 2008. [cited by applicant]
PatHelland's Weblog, published Jun. 14, 2007, “Accountants Don't Use Erasers”. http://blogs.msdn.com/pathelland/archive/2007/06/14/accountants-don-t-use-erasers.aspx. [cited by applicant]
Daniel J. Abadi; Samuel R. Madden; and Miguel C. Ferreira, “Integrating Compression and Execution in Column-Oriented Database Systems”, SIGMOD 2006, Jun. 27-29, 2006, Chicago, Illinois. [cited by applicant]
MDX Data Manipulation Statements (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms144786(printer).aspx. [cited by applicant]
MDX Data Definition Statements (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms144926(printer).aspx. [cited by applicant]
Functions (MDX Syntax), 2008. http://msdn.microsoft.com/en-us/library/ms145563(printer).aspx. [cited by applicant]
MDX Language Reference (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145595(printer).aspx. [cited by applicant]
MDX Function Reference (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145970(printer).aspx. [cited by applicant]
Working with Members, ples, and Sets (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms146040(printer).aspx. [cited by applicant]
MDX Syntax Conventions (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms144760(printer).aspx. [cited by applicant]
Operators (MDX Syntax), 2008. http://msdn.microsoft.com/en-us/library/ms144825(printer).aspx. [cited by applicant]
MDX Scripting Statements (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145482(printer).aspx. [cited by applicant]
Identifiers (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145572(printer).aspx. [cited by applicant]
MDX Statement Reference (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145610(printer).aspx. [cited by applicant]
Expressions (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms145971(printer).aspx. [cited by applicant]
MDX Operator Reference (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms144766(printer).aspx. [cited by applicant]
Reserved Keywords (MDX Syntax), 2008. http://msdn.microsoft.com/en-us/library/ms144887(printer).aspx. [cited by applicant]
Multidimensional Expressions (MDX) Reference, 2008. http://msdn.microsoft.com/en-us/library/ms145506(printer).aspx. [cited by applicant]
Comments (MDX Syntax), 2008. http://msdn.microsoft.com/en-us/library/ms145585(printer).aspx. [cited by applicant]
MDX Reserved Words, 2008. http://msdn.microsoft.com/en-us/library/ms145629(printer).aspx. [cited by applicant]
MDX Syntax Elements (MDX), 2008. http://msdn.microsoft.com/en-us/library/ms146020(printer).aspx. [cited by applicant]
Jovanka Adzic and Valter Fiore, “Data Warehouse Population Platform,” Lecture Notes in Computer Science (LNCS), 2209, 2001. [cited by applicant]
Itamar Ankorion, Change Data Capture—Efficient ETL for Real-Time BI; DM Review Magazine, Jan. 2005. [cited by applicant]
P. Boncz, “Monet: A Next-Generation DBMS Kernel for Query-Intensive Applications.” PHD Thesis, Universiteit van Amsterdam, Amsterdam, Netherlands, May 2002. [cited by applicant]
S. Brobst. “Enterprise Application Integration and Active Data Warehousing.” In Proceedings of Data Warehousing 2002, pp. 15-23, Heidelberg, Germany, 2000. Physica-Verlag GmbH. [cited by applicant]
F. Chang, J. Dean, S.Ghemawat, W.C. Hsieh, D.A. Wallach, M. Burrows, T. Chandra, A. Fikes, and R.E. Gruber, “Bigtable: A Distributed Storage System for Structured Data.” In USENIX'06: Proceedings of the 7th Conf. on USE… [cited by applicant]
E.F. Codd, “A Relational Model of Data for Large Shared Data Banks.” Communications of the ACM, 13:377-387, Jun. 1970. [cited by applicant]
J.F. Gantz et al., “The Expanding Digital Universe: A Forecast of Worldwide Information Growth Through 2010.” IDC White Paper, Mar. 2007. [cited by applicant]
W.H. Inmon, “When are Star Schemas Okay in a Data Warehouse?” B-Eye: Business Intelligence Network—The Global Vision for BI and Beyond, Jul. 2007. [cited by applicant]
T. Legler, W. Lehner, and A. Ross, “Data Mining with the SAP NetWeaver BI Accelerator.” In VLDB '06: Proceedings of the 32nd International Conference on Very Large Data Bases, pp. 1059-1068. VLDB Endowment, 2006. [cited by applicant]
W. Liang and J.X. Yu, “Revisit on View Maintenance in Data Warehouses.” In WAIM '01: Proceedings of the Second International Conference on Advances in Web-Age Information Management, 2001. [cited by applicant]
M. Stonebraker et al., “C-Store: A Column-oriented DBMS,” in VLDB '05: Proceedings of the 31st International Conference on Very Large Data Bases, pp. 553-564. VLDB endowment, 2005. [cited by applicant]
K. Becker and D.D.A. Ruiz. An Aggregate-Aware Retargeting Algorithm for Multiple Fact Data Warehouses. In Yahiko Kambayashi and Mukesh K. Mohania and Wolfram WÖß, editor, DaWaK, vol. 3181 of Lecture Notes in Computer Sc… [cited by applicant]
G.P. Copeland and s. Khoshafian. A Decomposition Storage Model. In S.B. Navathe, editor, Proceedings of the 1985 ACM SIGMOD International Conference on Management of Data, Austin, Texas, May 28-31, 1985, pp. 268-279. AC… [cited by applicant]
W.H. Inmon. Information Management: World-Class Business Intelligence. DM Review Magazine, Mar. 2000. [cited by applicant]
W.H. Inmon. Building the Data Warehouse, 3rd Edition. John Wiley & Sons, Inc., New York, NY, USA, 2002. [cited by applicant]
R. Kimball and J. Caserta. The Data Warehouse ETL Toolkit: Practical Techniques for Extracting, Cleaning. John Wiley & Sons, Inc., New York, NY, USA, 2004. [cited by applicant]
A. Knöpfel, B. Gröne, and P. Tabeling. Fundamental Modeling Concepts: Effective Communication of IT Systems. John Wiley & Sons, Inc., May 2006. [cited by applicant]
N.R. Mahapatra and B. Venkatrao. The Processor-Memory Bottleneck: Problems and Solutions. Crossroads, 5(3):2, 1999. [cited by applicant]
L.T. Moss and S. Atre. Business Intelligence Roadmap: The Complete Project Lifecycle for Decision-Support Applications. Addison-Wesley, 2003. [cited by applicant]
A. Y. Noaman and K. Barker. A Horizontal Fragmentation Algorithm for the Fact Relation in a Distributed Data Warehouse. In CIKM '99: Proceedings of the Eighth International Conference on Information and Knowledge Manage… [cited by applicant]
N.H. Rasmussen, P.S. Goldy, and P.O. Solli. Financial Business Intelligence: Trends, Technology, Software Selection, and Implementation. John Wiley & Sons, Inc., New York, NY, USA, 2002. [cited by applicant]
A Simitsis, P. Vassiliadis, and T. Sellis. State-Space Optimization of ETL Workflows. IEEE Transactions on Knowledge and Data Engineering, 17(10):1404-1419, 2005. [cited by applicant]
C. Yu. High-Dimensional Indexing: Transformational Approaches to High-Dimensional Range and Similarity Searches, vol. 2341/2002. Springer-Verlag New York, Inc., Secaucus, NJ, USA, 2002. [cited by applicant]
Daniel J. Abadi, Peter A. Boncz, and Stavros Harizopoulos, “Column-Oriented Database Systems,” VLDB '09, pp. 1664-1665, Aug. 24-28, 2009. [cited by applicant]
W.H. Inmon. Building the Data Warehouse, 3rd Edition. pp. 29-30,32, and 126. John Wiley & Sons, Inc., New York, NY, USA, 2002. [cited by applicant]
R. Kimball and J. Caserta. The Data Warehouse ETL Toolkit: Practical Techniques for Extracting, Cleaning. John Wiley & Sons, Inc., pp. 426-428, New York, NY, USA, 2004. [cited by applicant]
A. Knöpfel, B. Gröne, and P. Tabeling. Fundamental Modeling Concepts: Effective Communication of IT Systems. Appendix B, pp. 300-301. John Wiley & Sons, Inc., May 2006. [cited by applicant]
L.T. Moss and S. Atre. Business Intelligence Roadmap: The Complete Project Lifecycle for Decision-Support Applications. pp. 228-229, Addison-Wesley, 2003. [cited by applicant]
N.H. Rasmussen, P.S. Goldy, and P.O. Solli. Financial Business Intelligence: Trends, Technology, Software Selection, and Implementation. pp. 96-97, John Wiley & Sons, Inc., New York, NY, USA, 2002. [cited by applicant]