Operational data store: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 15:16, 10 October 2017 edit 193.194.132.70 (talk) No edit summary ← Previous edit		Latest revision as of 04:16, 2 March 2024 edit undo Urban Versis 32 (talk \| contribs) Extended confirmed users, Pending changes reviewers 5,185 edits 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" Tag: Shortdesc helper
(35 intermediate revisions by 23 users not shown)
Line 1: {{Short description\|Type of operational reporting database}} ~~{{unsourced\|date=August 2017}}~~ {{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]] ~~landscape~~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 ~~'''operational~~ODS ~~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.▼ An operational data store should not be confused with an enterprise data hub (EDH). An operational data store will take transactional data from one or more production system 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.▼ ▲An ~~operational data store~~ODS should not be confused with an enterprise [[data hub]] (EDH). An operational data store will take transactional data from one or more production ~~system~~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. An ODS is not an intrinsic part of an Enterprise Data Hub solution, although an EDH may be used to subsume some of the processing performed by an ODS and the Enterprise Data Warehouse. An EDH is a broker of data. An ODS is certainly not.▼ ▲An ODS is not an intrinsic part of an ~~Enterprise Data Hub~~EDH solution, although an EDH may be used to subsume some of the processing performed by an ODS and the ~~Enterprise Data Warehouse~~EDW. An EDH is a broker of data. An ODS is certainly not. ▲An '''operational 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 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~~originates 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 use== Line 16 ⟶ 17: ==See also== * Some examples of ODS ~~Architecture~~architecture ~~Patterns~~patterns can be found in the article [[Architectural pattern (computer science)#Examples\|Architecture ~~Patterns~~patterns]].▼ ~~{{Wikipedia books\|Enterprise Architecture}}~~ ▲* Some examples of ODS Architecture Patterns can be found in the article [[Architectural pattern (computer science)#Examples\|Architecture Patterns]]. * [[Enterprise architecture]] * [[Third normal form]] (3NF) ==Further 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=~~Information~~Crystal ~~Management~~Clear ~~article~~Customers: onThe ~~ODS}}{{~~Role of the Operational Data Store \|url-status=dead ~~link~~\|~~date~~archiveurl=https://web.archive.org/web/20160304073837/http://www.intelsols.com/documents/Imhoff_10-02.pdf \|archivedate=~~September~~2016-03-04 ~~2017~~}}<!--assuming wrong title and content, not even PDF--> ▲==Further 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}} {{Data warehouse}} {{DEFAULTSORT:Operational Data Store}} [[Category:Data management]] [[Category:Data warehousing]] [[Category:Management cybernetics]] ~~{{database-stub}}~~