Revision as of 12:12, 13 November 2018 edit 159.220.74.6 (talk) No edit summary ← Previous edit		Revision as of 12:14, 13 November 2018 edit undo 159.220.74.6 (talk) No edit summary Next edit →
Line 1: {{unsourced\|date=August 2017}} An '''operational data store''' (or "'''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]], 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 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 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 ~~'''~~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 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.

Operational data store: Difference between revisions