Diferensa entre baze dadus operasionál no armazén dadus

Baze dadus operasionál mak fonte informasaun ba armazén dadus. Ne’e inklui informasaun detalladu ne’ebé uza atu hala’o operasaun loron-loron ba negósiu. Dadus sira-ne’e muda beibeik bainhira halo atualizasaun no reflete valór atuál husi tranzasaun ikus sira.

Sistema Jestaun Baze Dadus Operasional mós bolu hanesan OLTP (Online Transactions Processamentu Baze Dadus), uza atu jere dadus dinámiku iha tempu real.

Sistema armazenamentu dadus serve utilizadór ka traballador koñesimentu sira ho objetivu atu halo análize dadus no foti desizaun. Sistema hirak-ne’e bele organiza no aprezenta informasaun iha formatu espesífiku sira atu bele akompaña nesesidade oioin husi utilizadór oioin. Sistema hirak-ne’e bolu nu’udar Sistema Prosesu Analitiku online (OLAP).

 Armazén dadus no baze dadus OLTP nian mak baze dadus relasionál rua. Maibé, ne’e.

Operational DatabaseData Warehouse
Operational systems are designed to support high-volume transaction processing.Data warehousing systems are typically designed to support high-volume analytical processing (i.e., OLAP).
Operational systems are usually concerned with current data.Data warehousing systems are usually concerned with historical data.
Data within operational systems are mainly updated regularly according to need.Non-volatile, new data may be added regularly. Once Added rarely changed.
It is designed for real-time business dealing and processes.It is designed for analysis of business measures by subject area, categories, and attributes.
It is optimized for a simple set of transactions, generally adding or retrieving a single row at a time per table.It is optimized for extent loads and high, complex, unpredictable queries that access many rows per table.
It is optimized for validation of incoming information during transactions, uses validation data tables.Loaded with consistent, valid information, requires no real-time validation.
It supports thousands of concurrent clients.It supports a few concurrent clients relative to OLTP.
Operational systems are widely process-oriented.Data warehousing systems are widely subject-oriented
Operational systems are usually optimized to perform fast inserts and updates of associatively small volumes of data.Data warehousing systems are usually optimized to perform fast retrievals of relatively high volumes of data.
Data InData Out
Less Number of data accessed.Large Number of data accessed.
Relational databases are created for on-line transactional Processing (OLTP)Data Warehouse designed for on-line Analytical Processing (OLAP)

Diferensa entre OLTP no OLAP

Sistema OLTP

Sistema OLTP trata ho dadus operasionál. Dadus operasionál mak dadus ne’ebé iha iha sistema ida-idak nia operasaun. Ezemplu, tranzasaun ATM no tranzasaun Banku, etc.

Sistema OLAP

OLAP trata ho Dadus Istorikus ka Dadus Arkivu. Dadus istóriku mak dadus ne’ebé hetan durante períodu naruk. Porezemplu, se ita halibur informasaun kona-ba rezerva aviaun iha tinan 10 nia laran, dadus sira-ne’e bele fó dadus signifikativu barak ba ita hanesan tendénsia iha rezerva. Ida ne’e bele fornese informasaun util hanesan tempu viajen ne’ebé di’ak liu, ema oinsá mak halo viajen iha klase oin-oin (Ekonomia/ Negosiu) etc.

 Diferensa boot entre sistema OLTP no OLAP mak montante dadus ne’ebé analiza ona iha tranzasaun ida deit. Enkuantu OLTP ida jere kliente no pergunta barak ne’ebé kompetente kona de’it rejistu individuál ka grupu arkivu limitadu iha tempu ida. Sistema OLAP ida tenke iha kapasidade atu opera iha arkivu millaun ida atu hatán ba pergunta ida deit.

FeatureOLTPOLAP
CharacteristicIt is a system which is used to manage operational Data.It is a system which is used to manage informational Data.
UsersClerks, clients, and information technology professionals.Knowledge workers, including managers, executives, and analysts.
System orientationOLTP system is a customer-oriented, transaction, and query processing are done by clerks, clients, and information technology professionals.OLAP system is market-oriented, knowledge workers including managers, do data analysts executive and analysts.
Data contentsOLTP system manages current data that too detailed and are used for decision making.OLAP system manages a large amount of historical data, provides facilitates for summarization and aggregation, and stores and manages data at different levels of granularity. This information makes the data more comfortable to use in informed decision making.
Database Size100 MB-GB100 GB-TB
Database designOLTP system usually uses an entity-relationship (ER) data model and application-oriented database design.OLAP system typically uses either a star or snowflake model and subject-oriented database design.
ViewOLTP system focuses primarily on the current data within an enterprise or department, without referring to historical information or data in different organizations.OLAP system often spans multiple versions of a database schema, due to the evolutionary process of an organization. OLAP systems also deal with data that originates from various organizations, integrating information from many data stores.
Volume of dataNot very largeBecause of their large volume, OLAP data are stored on multiple storage media.
Access patternsThe access patterns of an OLTP system subsist mainly of short, atomic transactions. Such a system requires concurrency control and recovery techniques.Accesses to OLAP systems are mostly read-only methods because of these data warehouses stores historical data.
Access modeRead/writeMostly write
Insert and UpdatesShort and fast inserts and updates proposed by end-users.Periodic long-running batch jobs refresh the data.
Number of records accessedTensMillions
NormalizationFully NormalizedPartially Normalized
Processing SpeedVery FastIt depends on the amount of files contained, batch data refresh, and complex query may take many hours, and query speed can be upgraded by creating indexes.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *