Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1


Ratings: (0)|Views: 1,466 |Likes:
Published by Deepanshu

More info:

Published by: Deepanshu on Jul 13, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





March 5, 2009 byDeepanshu Mehta We can divide IT systems into transactional (OLTP) and analytical (OLAP). In generalwe can assume that OLTP systems provide source data to data warehouses, whereasOLAP systems help to analyze it.
OLTP (On-line Transaction Processing)
is characterized by a large number of short on-line transactions (INSERT, UPDATE, DELETE). The main emphasis for OLTP systemsis put on very fast query processing, maintaining data integrity in multi-accessenvironments and an effectiveness measured by number of transactions per second.
OLAP (On-line Analytical Processing)
is characterized by relatively low volume of transactions. Queries are often very complex and involve aggregations. For OLAPsystems a response time is an effectiveness measure. OLAP applications are widely used by Data Mining techniques.The following table summarizes the major differences between OLTP and OLAP systemdesign.
OLTP SystemOnline Transaction Processing(Operational System)OLAP SystemOnline Analytical Processing(Data Warehouse)Source of dataOperational data; OLTPs are theoriginal source of the data.Consolidation data; OLAP data comesfrom the various OLTP DatabasesPurpose of dataTo control and run fundamental business tasksTo help with planning, problemsolving, and decision supportWhat the dataReveals a snapshot of ongoing business processesMulti-dimensional views of variouskinds of business activitiesInserts andUpdatesShort and fast inserts and updatesinitiated by end usersPeriodic long-running batch jobsrefresh the dataQueriesRelatively standardized and simplequeries Returning relatively fewrecordsOften complex queries involvingaggregationsProcessingSpeedTypically very fastDepends on the amount of datainvolved; batch data refreshes andcomplex queries may take manyhours; query speed can be improved by creating indexesSpaceRequirementsCan be relatively small if historicaldata is archivedLarger due to the existence of aggregation structures and historydata; requires more indexes thanOLTPDatabase Highly normalized with many Typically de-normalized with fewer 

Activity (11)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Bhaskar Boss liked this
Musa Ali Sheikh liked this
TEJASKO liked this
raghu371 liked this
mohanvamsi_18 liked this
Sandeep liked this
Kanchan Samant liked this
autocratic liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->