imported>Rofraja: No bare URLs. Remove Cleanup bare URLs template

2024-12-07T13:33:25Z

No bare URLs. Remove Cleanup bare URLs template

New page

{{Short description|Database system for real time data updates}}
{{more footnotes needed|date=March 2013}}

'''Operational [[database]] management systems''' (also referred to as '''[[OLTP]] databases''' or '''online transaction processing databases'''), are used to update data in real-time. These types of databases allow users to do more than simply view archived data. Operational databases allow you to modify that data (add, change or delete data), doing it in [[Real-time computing|real-time]].<ref name="Techopedia">{{cite web|url=https://www.techopedia.com/definition/5711/operational-database-odb |title=Operational Database (ODB)|date=15 November 2016 |publisher=Techopedia}}</ref> OLTP databases provide [[Database transaction|transactions]] as main abstraction to guarantee data consistency that guarantee the so-called [[ACID properties]]. Basically, the consistency of the data is guaranteed in the case of failures and/or concurrent access to the data.

== History ==
Since the early 1990s, the operational database software market has been largely taken over by [[SQL]] engines. In 2014, the operational [[DBMS]] market (formerly [[OLTP]]) was evolving dramatically, with new, innovative entrants and incumbents supporting the growing use of [[unstructured data]] and [[NoSQL]] DBMS engines, as well as [[XML database]]s and [[NewSQL|NewSQL databases]]. NoSQL databases typically have focused on scalability and have renounced to data consistency by not providing transactions as OLTP system do. Operational databases are increasingly supporting [[distributed database]]<ref>{{Cite book|title=Principles of Distributed Databases|last1=Ozsu|first1=M. Tamer|last2=Valduriez|first2=Patrick|publisher=Springer|year=2011|isbn=978-1-4419-8833-1}}</ref> architecture that can leverage distribution to provide [[high availability]] and [[fault tolerance]] through [[replication (computing)|replication]] and [[scale out]] ability.

The growing role of operational databases in the [[information technology|IT]] industry is moving fast from legacy databases to real-time operational databases capable to handle distributed web and mobile demand and to address [[Big data]] challenges. Recognizing this, [[Gartner]] started to publish the [[Magic Quadrant]] for Operational Database Management Systems in October 2013.<ref name="Gartner Magic Quadrant for Operational Database Management Systems">{{cite web|url=https://www.gartner.com/doc/2610218/magic-quadrant-operational-database-management |title=Gartner Magic Quadrant for Operational Database Management Systems|publisher=Gartner.com}}</ref>

== List of operational databases ==

Notable operational databases include:

{| style="text-align: left;" class="wikitable sortable"
|-
! Database platform !! Database model !! [[SQL]] Support !! [[NoSQL]] Support !! Managed objects !! ACID-transactions
|-
| [[Aerospike (database)|Aerospike]] || Key–value store || No || '''Yes''' || key-value pairs || None
|-
| [[Altibase]] || Relational database || '''Yes''' || No || tabular data || ACID transactions
|-
| [[Apache Cassandra]] || Key–value store || No || '''Yes''' || key–value pairs || None
|-
|[[Apache HBase]]
|Key–value store
|'''Yes''' (Phoenix)
|'''Yes'''
|key–value pairs
|ACID-transactions
|-
| [[Cloudant]] || Document-oriented database || No || '''Yes''' || JSON || None
|-
| [[Clusterpoint]] || Document-oriented database || '''Yes''' (essential SQL) || '''Yes''' || XML, JSON, text data || Distributed ACID-transactions
|-
| [[Clustrix]] || Relational database || '''Yes''' (newSQL) || No || tabular data || ACID-transactions
|-
| [[Couchbase]] || Document-oriented database || '''Yes''' (N1QL) || '''Yes''' || JSON, key–value pairs || Distributed Multi-Document ACID transactions
|-
| [[CouchDB]] || Document-oriented database || No || '''Yes''' || JSON || None
|-
|[[IBM Db2]] || Relational database, Data Warehouse || '''Yes''' || '''Yes''' || JSON, key–value pairs, tabular data, XML || ACID-transactions
|-
| [[EnterpriseDB]] || Relational database || '''Yes''' || No || tabular data || ACID-transactions
|-
| [[FoundationDB]] || Key–value store || '''Yes''' || No || key–value pairs || ACID-transactions
|-
| [[Ingres (database)|Ingres]] || Relational database || '''Yes''' || No || tabular data || ACID-transactions
|-
| [[MarkLogic]] || Document-oriented database || Yes || '''Yes''' ([[XQuery]] and JavaScript) || XML and JSON || ACID-transactions
|-
| [[Microsoft SQL Server]] || Relational database || '''Yes''' || No || tabular data || ACID-transactions
|-
| [[MongoDB]] || Document-oriented database || No || '''Yes''' || BSON || None
|-
| [[NuoDB]] || Relational database || '''Yes''' (newSQL) || No || tabular data || ACID-transactions
|-
| [[Oracle Database|Oracle]] || Relational database || '''Yes''' || Yes || multi-model || ACID-transactions
|-
| [[OrientDB]] || Document-oriented Database || '''Yes''' || Yes || key–value pairs || ACID-transactions<ref>{{Cite web |url=http://orientdb.com/docs/last/Transactions.html |title=Archived copy |access-date=2016-03-25 |archive-date=2016-03-25 |archive-url=https://web.archive.org/web/20160325204447/http://orientdb.com/docs/last/Transactions.html |url-status=dead }}</ref>
|-
| [[Riak]] || Key–value store || No || '''Yes''' || key–value pairs || None
|-
| [[SAP HANA]] || Relational database || '''Yes''' || No || tabular data || ACID-transactions
|-
| [[ScyllaDB]] || Key–value store || No || '''Yes''' || key–value pairs || None
|-
| [[VoltDB]] || Relational database || '''Yes''' (newSQL) || No || tabular data || ACID-transactions
|-
| [[YugabyteDB]] || Relational database (YSQL), Key–value store (YCQL) || '''Yes''' (newSQL) || '''Yes''' || tabular data, JSON || ACID-transactions
|}

== Use in business ==

Operational databases are used to store, manage and track real-time business information. For example, a company might have an operational database used to track warehouse/stock quantities. As customers order products from an online web store, an operational database can be used to keep track of how many items have been sold and when the company will need to reorder stock. An '''operational database''' stores information about the activities of an [[organization]], for example [[customer relationship management]] transactions or financial operations, in a computer [[database]].

Operational databases allow a business to enter, gather, and retrieve large quantities of specific information, such as company legal data, financial data, call data records, personal employee information, sales data, customer data, data on assets and many other information. An important feature of storing information in an operational database is the ability to share information across the company and over the Internet. Operational databases can be used to manage mission-critical business data, to monitor activities, to audit suspicious transactions, or to review the history of dealings with a particular customer. They can also be part of the actual process of making and fulfilling a purchase, for example in [[e-commerce]].

==Data warehouse terminology==

In [[Data warehouse|data warehousing]], the term is even more specific: the operational database is the one which is accessed by an [[operational system]] (for example a customer-facing website or the application used by the customer service department) to carry out regular operations of an organization. Operational databases usually use an [[online transaction processing]] database which is optimized for faster transaction processing ([[create, read, update and delete]] operations). An operational database is the source for a data warehouse.<ref name="Techopedia" /> Data from an operational database can be loaded into an [[operational data store]] at a data warehouse before the data is processed into the data warehouse.

== See also ==
* [[Distributed database]]
* [[Document-oriented database]]
* [[Hybrid Transactional/Analytical Processing (HTAP)|HTAP database]]
* [[NewSQL|NewSQL database]]
* [[NoSQL|NoSQL database]]
* [[Real-time database]]
* [[SQL|SQL database]]
* [[XML|XML database]]

== References ==
{{Reflist|33em}}
* O’Brien, Jason., and Marakas, Gorila., (2008). Management Information Technology Systems. Computer Software (pp. 185). New York, New York: McGraw-Hill

[[Category:Data warehousing]]
[[Category:Data management]]
[[Category:Business intelligence]]
[[Category:Types of databases]]

Operational database - Revision history

imported>Rofraja: No bare URLs. Remove Cleanup bare URLs template