Data Warehousing is a technique that is generally used to collect and manage data from multiple sources to provide the business a meaningful business insight. A data warehouse is specifically created for the goals of support management decisions.
In simple terms, a data warehouse defines a database that is maintained independently from an organization’s operational databases. Data warehouse systems enable the integration of several application systems. They provide data processing by supporting a solid platform of consolidated, historical data for analysis.
A data warehouse provides an OLTP system by supporting a place for the OLTP database to offload data as it accumulates, and by supporting services that can complicate and degrade OLTP operations if they were implemented in the OLTP database.
OLTP (Online Transaction Processing) is featured by a huge number of short on-line transactions (INSERT, UPDATE, and DELETE). The basic meaning of OLTP operations is put on very rapid query processing, maintaining record integrity in multi-access environments, and effectiveness dependable by the number of transactions per second. In the OLTP database, there is authentic and current data, and the schema used to store transactional database is the entity model (usually 3NF).
The main features of the OLTP database are simply controlled insertion and updating of data with effective access to data manipulation and viewing mechanisms. Generally, only single record or small record sets should be manipulated in an individual operation in an OLTP-designed database.
OLTP systems generally deal only with the current status of data. For instance, a record about an employee who left three years ago cannot be suitable on the Human Resources System. The old data can have been achieved on several kinds of stable storage media and cannot be accessible online.
Let us see the comparison between the Data Warehouse database and the OLTP database.
|Data Warehouse Database||OLTP Database|
|It is produced for analysis of business measures by categories and attributes.||It is produced for real-time business operations.|
|It can be optimized for the number of loads and large, complex, unpredictable queries that access several rows per table.||It can be optimized for a common set of transactions, generally inserting or retrieving a single row at a time per table.|
|It can be loaded with consistent, true data and needed no real-time validation.||It can be developed for the validation of incoming data during transactions and uses validation data tables.|
|It provides some concurrent users relative to OLTP.||It provides thousands of concurrent users.|