Why are OLTP database designs not generally a good idea for a Data Warehouse
Answer posted by Shri Dana on 2005-04-06 19:04:05: OLTP cannot store historical information about the organization. It is used for storing the details of daily transactions while a datawarehouse is a huge storage of historical information obtained from different datamarts for making intelligent decisions about the organization.
RE: Why are OLTP database designs not generally a good idea for a Data Warehouse
OLTP cannot store historical information about the organization. It is used for storing the details of daily transactions while a datawarehouse is a huge storage of historical information obtained from different datamarts for making intelligent decisions about the organization.
RE: Why are OLTP database designs not generally a good...
The data warehouse obtains data from one or more source systems which could be OLTP systems. So it could happen that the OLTP system and the data warehouse contain the same data. What distinguishes the data warehouse from the OLTP system is the data organisation. The data warehouse organises its data for query, analysis and reporting.
RE: Why are OLTP database designs not generally a good...
Because OLTP databases are transactional data related databases. The meaning of this is these databases are used in real time to insert, update and delete data. To accomplish these tasks in real time, The model used in OLTP databases is highly normalized. The problem of using this model in Data Warehousing is, we have to join multiple tables to get a single piece of data. With the amount of historical data we deal with in DW, it is highly desirable not to have a highly normalized data model like OLTP.
