2 replies
by t. e. walker
by carlos nunes
I disagree with the previous comment. Although T.E. Rutter's comments regarding the outsourcing of the warehouse, as a remote repository for a company's data, may actually be the case for some organizations, it does not correctly describe what a data warehouse is. The classic textbook description from William H. Inmon in Building the Data Warehouse (QED Technical Publishing Group, 1992, ISBN: 0-89435404-3) defines a data warehouse as "a collection of integrated, subject-oriented databases designed to supply the information required for decision-making". If you don't have a brain-freeze yet, the idea is that data are extracted from a business' various source systems into a single, integrated database. The data within this single databaseis organized by business subjects, allowing the database model to be better aligned with the way a decision-making business user would want to query the data. The data warehouse is designed as a tactical and strategic decision making system and is not intended to be used as a transactional system.
As for work in the field, there are a variety of jobs, as is the case in most database projects, but here are three of the most essential. The first is Project Management, few large scale development function without formal project management. The second is data architecture which requires good DB skills for a well-designed and efficient database. The third is Extract/Transform/Load (ETL) development which can at time require the writing of procedural code but often makes use of third party business tools to move the data from the various source systems to the data warehouse. The fourth is developing end-user views of the data. Any programming tools can be used but a trend exists tomake use of packaged OLAP (On-Line Analytical Processing) tools for advanced data querying and data visualization.
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending