Operational data store: Difference between revisions

Content deleted Content added
No edit summary
Adding local short description: "Type of operational reporting database", overriding Wikidata description "database used for operational reporting and incoming data source for the Enterprise Data Warehouse"
 
(45 intermediate revisions by 31 users not shown)
Line 1:
{{Short description|Type of operational reporting database}}
An '''operational data store''' (or "'''ODS'''") is a [[database]] designed to [[data integration|integrate data]] from multiple sources for additional operations on the data. Unlike a master data store, the data is not passed back to [[operational system]]s. It may be passed for further operations and to the [[data warehouse]] for reporting.
{{No footnotes|date=April 2023}}
An '''operational data store''' ('''ODS''') is used for operational reporting and as a source of data for the [[enterprise data warehouse]] (EDW). It is a complementary element to an EDW in a [[decision support]] environment, and is used for operational reporting, controls, and decision making, as opposed to the EDW, which is used for tactical and strategic decision support.
 
An '''operationalODS data store''' (or "'''ODS'''") is a [[database]] designed to [[data integration|integrate data]] from multiple sources for additional operations on the data, for reporting, controls and operational decision support. Unlike a production [[Master data management|master data store]], the data is not passed back to [[operational system]]s. It may be passed for further operations and to the [[data warehouse]] for reporting.
Because the [[data]] originate from multiple sources, the integration often involves [[data cleaning|cleaning]], resolving redundancy and checking against [[business rule]]s for [[data integrity|integrity]]. An ODS is usually designed to contain low-level or atomic (indivisible) data (such as transactions and prices) with limited history that is captured "real time" or "near real time" as opposed to the much greater volumes of data stored in the data warehouse generally on a less-frequent basis.
 
An ODS should not be confused with an enterprise [[data hub]] (EDH). An operational data store will take transactional data from one or more production systems and loosely integrate it, in some respects it is still subject oriented, integrated and time variant, but without the volatility constraints. This integration is mainly achieved through the use of EDW structures and content.
==General Use==
The general purpose of an ODS is to integrate data from disparate source systems in a single structure, using [[data integration]] technologies like [[Data Virtualization|data virtualization]], [[Federated database system|data federation]], or [[Extract, transform, load|extract, transform, and load]]. This will allow operational access to the data for operational reporting, [[Master Data|master data or reference data management]].
 
An ODS is not an intrinsic part of an EDH solution, although an EDH may be used to subsume some of the processing performed by an ODS and the EDW. An EDH is a broker of data. An ODS is certainly not.
An ODS is not a replacement or substitute for a [[data warehouse]] but in turn could become a source.
 
Because the [[data]] originateoriginates from multiple sources, the integration often involves [[data cleaning|cleaning]], resolving redundancy and checking against [[business rule]]s for [[data integrity|integrity]]. An ODS is usually designed to contain low-level or atomic (indivisible) data (such as transactions and prices) with limited history that is captured "real time" or "near real time" as opposed to the much greater volumes of data stored in the data warehouse generally on a less-frequent basis.
 
==General Useuse==
The general purpose of an ODS is to integrate data from disparate source systems in a single structure, using [[data integration]] technologies like [[Data Virtualization|data virtualization]], [[Federated database system|data federation]], or [[Extract, transform, load|extract, transform, and load]] (ETL). This will allow operational access to the data for operational reporting, [[Master Data|master data or reference data management]].
 
An ODS is not a replacement or substitute for a [[data warehouse]] or for a [[data hub]] but in turn could become a source.
 
==See also==
* Some examples of ODS Architecturearchitecture Patternspatterns can be found in the article [[Architectural pattern (computer science)#Examples|Architecture Patternspatterns]].
* [[Enterprise architecture]]
* [[Third normal form]] (3NF)
 
==PublicationsFurther reading==
* {{cite book |last1=Inmon |first1=William |author1-link=Bill Inmon |title=Building the Operational Data Store |edition=2nd |location=New York |publisher=[[John Wiley & Sons]] |year=1999 |isbn=0-471-32888-X}}
 
==External links==
*[[Architectural pattern (computer science)#Examples|ODS Architecture Patterns (EA Reference Architecture)]]
* [http://www.dmreview.com/issues/19980701/469-1.html Bill Inmon Information Management article on ODS]
* [http://www.information-management.com/issues/20000101/1749-1.html Bill Inmon Information Management article on the five classes of ODS]
* {{cite web |url=https://www.intelsols.com/documents/Imhoff_10-02.pdf |author=Claudia Imhoff |title=Crystal Clear Customers: The Role of the Operational Data Store |url-status=dead |archiveurl=https://web.archive.org/web/20160304073837/http://www.intelsols.com/documents/Imhoff_10-02.pdf |archivedate=2016-03-04 }}<!--assuming wrong title and content, not even PDF-->
* [http://www.intelsols.com/documents/Imhoff_10-02.pdf Claudia Imhoff Information Management article on ODS] PDF
 
{{Data warehouse}}
 
== See also ==
{{Wikipedia books|Enterprise Architecture}}
* [[Enterprise architecture]]
 
{{DEFAULTSORT:Operational Data Store}}
[[Category:Data management]]
[[Category:Data warehousing]]
[[Category:Management cybernetics]]
 
{{database-stub}}