Enterprise Data Warehouse Governance Best Practices
Additional contact information
Nayem Rahman: Intel Corporation, Hillsboro, OR, USA
International Journal of Knowledge-Based Organizations (IJKBO), 2016, vol. 6, issue 2, 21-37
Maintaining a stable data warehouse becomes quite a challenge if discipline is not applied to code development, code changes, code performance, system resource usage and configuration of integration specification. As the size of the data warehouse increases the value it brings to an organization tends to increase. However these benefits come at a cost of maintaining the applications and running the data warehouse efficiently on a twenty four hours a day and seven days a week basis. Governance is all about bringing discipline and control in the form of guidelines for application developers and IT integration engineers to follow, with a goal that the behavior of a data warehouse application becomes predictable and manageable. In this article the authors have defined and explained a set of data warehouse governance best practices based on their real-world experience and insights drawn from industry and academic papers. Data warehouse governance can also support the development life cycle, maintenance, data architecture, data quality assurance, the Sarbanes-Oxley (SOX) Act requirements and enforce business requirements.
References: Add references at CitEc
Citations Track citations by RSS feed
Downloads: (external link)
http://services.igi-global.com/resolvedoi/resolve. ... 018/IJKBO.2016040102 (application/pdf)
This item may be available elsewhere in EconPapers: Search for items with the same title.
Export reference: BibTeX
RIS (EndNote, ProCite, RefMan)
Persistent link: https://EconPapers.repec.org/RePEc:igg:jkbo00:v:6:y:2016:i:2:p:21-37
Access Statistics for this article
International Journal of Knowledge-Based Organizations (IJKBO) is currently edited by John Wang
More articles in International Journal of Knowledge-Based Organizations (IJKBO) from IGI Global
Series data maintained by Journal Editor ().