September 2001
Beginner
544 pages
17h 43m
English
Content preview from DATA WAREHOUSING FUNDAMENTALS: A Comprehensive Guide for IT Professionals
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
5.1. CHAPTER OBJECTIVES
Discuss how and why defining requirements is different for a data warehouse
Understand the role of business dimensions
Learn about information packages and their use in defining requirements
Review methods for gathering requirements
Grasp the significance of a formal requirements definition document
A data warehouse is an information delivery system. It is not about technology, but about solving users' problems and providing strategic information to the user. In the phase of defining requirements, you need to concentrate on what information the users need, not so much on how you are going to provide the required information. The actual methods for providing information will come later, not while you are collecting requirements.
Most of the developers of data warehouses come from a background of developing operational or OLTP (online transactions processing) systems. OLTP systems are primarily data capture systems. On the other hand, data warehouse systems are information delivery systems. When you begin to collect requirements for your proposed data warehouse, your mindset will have to be different. You have to go from a data capture model to an information delivery model. This difference will have to show through all phases of the data warehouse project.
The users also have a different perspective about a data warehouse system. Unlike an OLTP system which is needed to run the day-to-day business, no immediate payout is seen in a decision support system. The ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.