Today's next-generation data warehouses are being built with a clear goal: to maximize the power of Customer Relationship Management. To make CRM-focused data warehousing work, IT professionals need new techniques, and new methodologies. In this book, Dr. Chris Todman delivers the first start-to-finish methodology for defining, designing, and implementing CRM-focused data warehouses. Designing Data Warehouses: Supporting Customer Relationship Management starts by identifying critical design challenges that are unique to CRM-focused data warehousing. In the context of CRM, Todman reviews data warehouse conceptual models, logical models, and physical implementation, and focuses on the crucial implications of time in data warehouse modeling and querying. You'll discover how to estimate the ROI of CRM-focused data warehousing in advance; manage data warehouse projects more effectively; and select the right software for loading, extraction, transformation, querying, data mining, campaign management, personalization, and metadata. Finally, Todman previews the future of data warehousing, covering temporal databases, OLAP SQL extensions, active decision support, the integration of external and unstructured data, next-generation search agents, and more.
FREE Two-Day Shipping for students on millions of items. Learn more |
Book Description
Special Offers and Product Promotions
- Buy $50 in qualifying physical textbooks, get $5 in Amazon MP3 Credit. Here's how (restrictions apply)
Editorial Reviews
From the Inside Flap
Preface
The main subject of this book is data warehousing. A data warehouse is a special kind of database that, in recent years, has attracted a great deal of interest in the information technology industry. Quite a few books have been published about data warehousing generally, but very few have focused on the design of data warehouses. There are some notable exceptions, and these will be cited in this book, which concentrates, principally, on the design aspects of data warehousing.
Data warehousing is all about making information available. No one doubts the value of information, and everyone agrees that most organizations have a potential "Aladdin's Cave" of information that is locked away within their operational systems. A data warehouse can be the key that opens the door to this information.
There is strong evidence to suggest that our early foray in the field of data warehousing, what I refer to as first-generation data warehouses, has not been entirely successful. As is often the case with new ideas, especially in the information technology (IT) industry, the IT practitioners were quick to spot the potential, and they tried hard to secure the competitive advantage for their organizations that the data warehouse promised. In doing so I believe two points were overlooked. The first point is that, at first sight, a data warehouse can appear to be quite a simple application. In reality it is anything but simple. Quite apart from the basic issue of sheer scale (data warehouse databases are amongst the largest on earth) and the consequent performance difficulties presented by this, the data structures are inherently more complex than the early pioneers of these systems realized. As a result, there was a tendency to over-simplify the design so that, although the database was simple to understand and use, many important questions could not be asked.
The second point is that data warehouses are unlike other operational systems in that it is not possible to define the requirements precisely. This is at odds with conventional systems where it is the specification of requirements that drives the whole development lifecycle. Our approach to systems design is still, largely, founded on a thorough understanding of requirements-the "hard" systems approach. In data warehousing we often don't know what the problems are that we are trying to solve. Part of the role of the data warehouse should be to help organizations to understand what their problems are.
Ultimately it comes down to design and, again, there are two main points to consider. The first concerns the data warehouse itself. Just how do we ensure that the data structures will enable us to ask the difficult questions? Secondly, the hard systems approach has been shown to be too restrictive and a softer technique is required. So not only do we need to improve our design of data warehouses, we also need to improve the way in which we approach the design.
It is in response to these two needs that this book has been written.First generation data warehouses
Historically, the first-generation data warehouses were built on certain principles that were laid down by gurus in the industry. This author recognizes two great pioneers in data warehousing: Bill Inmon and Ralph Kimball. These two chaps, in my view, have done more to advance the development of data warehousing than any others. Although many claim to have been "doing data warehousing long before it was ever called data warehousing," Inmon and Kimball can realistically claim to be the founders because they alone laid down the definitions and design principles that most practitioners are aware of today. Even if their guidelines are not followed precisely, it is still common to refer to Inmon's definition of a data warehouse and Kimball's rules on slowly changing dimensions.
Chapter 2 of this book is an introduction to data warehousing. In some respects it should be regarded as a scene-setting chapter, as it introduces data warehouses from first principles by describing the following:
Need for decision support
How data warehouses can help
Differences between operational systems and data warehouses
Dimensional models
Main components of a data warehouse
Chapter 2 lays the foundation for the evolution to the second-generation data warehouses.Second-Generation Data Warehouses and Customer Relationship Management
Before the introduction to data warehousing, we take a look at the business issues in a kind of rough guide to customer relationship management (CRM). Data warehousing has been waiting for CRM to appear. Without it, data warehouses were still popular but, very often, the popularity was as much in the IT domain as anywhere else. The IT management was quick to see the potential of data warehouses, but the business justification was not always the main driver and this has led to the failure of some data warehouse projects. There was often a reluctance on the part of business executives to sponsor these large and expensive database development projects. Those that were sponsored by IT just didn't hit the spot. The advent of CRM changed all that. CRM cannot be practiced in business without a major source of information, which, of course, is the data warehouse raison d'etre. Interest in data warehousing has been revitalized, and this time it is the business people who are firmly in the driving seat.
Having introduced the concept of CRM and described its main components, we explore, with the benefit of hindsight, the flaws in the approach to designing first-generation data warehouses and will propose a method for the next generation. We start by examining some of the design issues and pick our way carefully through the more sensitive areas in which the debate has smoldered, if not raged a little, over the past several years. One of the fundamental issues surrounds the representation of time in our design. There has been very little real support for this, which is a shame, since data warehouses are true temporal applications that have become pervasive and ubiquitous in all kinds of businesses.
In formulating a solution, we reintroduce, from the mists of time, the old conceptual, logical, and physical approach to building data warehouses. There are good reasons why we should do this and, along the way, these reasons are aired.
We have a short chapter on the business justification. The message is clear. If you cannot justify the development of the data warehouse, then don't build it. No one will thank us for designing and developing a beautifully engineered, high-performing system if, ultimately, it cannot pay for itself within an appropriate time. Many data warehouses can justify themselves several times over, but some cannot. We do not want to add to the list of failed projects. Ultimately, no one benefits from this and we should be quite rigorous in the justification process.
Project management is a crucial part of a data warehouse development. The normal approach to project management doesn't work. There are many seasoned, top-drawer project managers who, in the beginning, are very uncomfortable with data warehouse projects. The uncertainty of the deliverables and the imprecise nature of the acceptance criteria send them howling for the safety net of the famous system specification. It is hoped that the chapter on project management will provide some guidance.
People who know me think I have a bit of a "down" on software products and if I'm honest I suppose I do. I get a little irritated when the same old query tools get dusted off and relaunched as each new thing comes along as though they are new products. Once upon a time a query tool was a query tool. Now it's a data mining product, a segmentation product, and a CRM product as well. OK, these vendors have to make a living but, as professional consultants, we have to protect our customers, particularly the gullible ones, from some of these vendors. Some of the products do add value and some, while being astronomically expensive, don't add much value at all. The chapter on software products sheds some light on the types of tools that are available, what they're good at, what they're not good at, and what the vendors won't tell you if you don't ask.Who Should Read This Book
Although there is a significant amount of technical material in the book, the potential audience is quite wide:
For anyone wishing to learn the principles of data warehousing, Chapter 2 has been adapted from undergraduate course material. It explains, in simple terms:
What data warehouses are
How they are used
The main components
The data warehouse "jargon"
There is also a description of some of the pitfalls and problems faced in the building of data warehouses.
For consultants, the book contains a method for ensuring that the business objectives will be met. The method is a top-down approach using proven workshop techniques. There is also a chapter devoted to assisting in the building of the business justification.
For developers of data warehouses, the book contains a massive amount of material about the design, especially in the area of the data model, the treatmen
From the Back Cover
The complete guide to building tomorrow's CRM-focused data warehouses.
- A complete methodology for building CRM-focused data warehouses
- Planning, ROI, conceptual and logical models, physical implementation, project management, and beyond
- For database developers, architects, consultants, project managers, and decision-makers
Today's next-generation data warehouses are being built with a clear goal: to maximize the power of Customer Relationship Management. To make CRM-focused data warehousing work, you need new techniques, and new methodologies. In this book, Dr. Chris Todman—one of the world's leading data warehouse consultants—delivers the first start-to-finish methodology for defining, designing, and implementing CRM-focused data warehouses. Todman covers all this, and more:
- Critical design challenges unique to CRM-focused data warehousing
- A new look at data warehouse conceptual models, logical models, and physical implementation
- The crucial implications of time in data warehouse modeling and querying
- Project management: deliverables, assumptions, risks, and team-building—including a full breakdown of work
- Estimating the ROI of CRM-focused data warehouses up front
- Choosing software for loading, extraction, transformation, querying, data mining, campaign management, personalization, and metadata
- DW futures: temporal databases, OLAP SQL extensions, active decision support, integrating external and unstructured data, search agents, and more
If you want to leverage the full power of your CRM system, you need a data warehouse designed for the purpose. One book shows you exactly how to build one: Designing Data Warehouses by Dr. Chris Todman.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
12 of 15 people found the following review helpful:
3.0 out of 5 stars
Sound advice and clear guidance,
By
This review is from: Designing A Data Warehouse: Supporting Customer Relationship Management (Paperback)
This book will help anyone embarking on a CRM project to at least get the Data Warehousing technical architecture right.According to the blurb "Today's next-generation data warehouses are being built with a clear goal: to maximize the power of Customer Relationship Management". Obviously something that confuses business benefit with techhnological features. It then goes on to state interesting and somewhat obvios things such as "To make CRM-focused data warehousing work, IT professionals need new techniques, and new methodologies". In this book, Dr. Chris Todman -- apparently one of HPs leading data warehouse consultants -- delivers the first start-to-finish methodology for defining, designing, and implementing CRM-focused data warehouses. Accordiing to the experts the support of Customer Relationship Management starts with identifying critical design challenges that are unique to CRM-focused data warehousing. In the context of CRM, Todman reviews data warehouse conceptual models, logical models, and physical implementation, and focuses on the crucial implications of time in data warehouse modeling and querying. You'll discover how to estimate the ROI of CRM-focused data warehousing in advance; manage data warehouse projects more effectively; and select the right software for loading, extraction, transformation, querying, data mining, campaign management, personalization, and metadata. Finally, Todman previews the future of data warehousing, covering temporal databases, OLAP SQL extensions, active decision support, the integration of external and unstructured data, next-generation search agents, and more. This is an almost complete methodology for building CRM-focused data warehouses, including elements of planning, ROI, conceptual and logical models, physical implementation, project management, and so-on. It is quite recommended for database developers, architects, consultants, project managers, and decision-makers. Although I have seen a lot of the ideas elsewhere - primarily in Hewlett-Packards proprietary OpenWarehouse methodology - this book weighs in with a substantially lower price tag. Regards, martyn_jones@iniciativas.com
3 of 3 people found the following review helpful:
5.0 out of 5 stars
How to build a CRM database with real history,
By A Customer
This review is from: Designing A Data Warehouse: Supporting Customer Relationship Management (Paperback)
We were having a real problem with the storage of real history in our CRM database. The other books we have either ignore the problem or treat it very superficially. We have found that, if we want to make predictions about customers, we need their historical data to enable us to do this effectively.This book is the only one we have found which takes the issue of time seriously. It has a complete chapter dealing with the issue and introduces some enlightening ideas in database design which we have adopted with good results. We also liked the no nonsense introduction to the analytical aspects of CRM. The whole book is written in an easy to read, chatty style which makes it pleasing to pick up. Also we have used the chapters on ROI and project management with positive results. There is an entire chapter on Requirements gathering, introducing a system called Dot Modelling which we plan to use - but haven't used yet.
7 of 9 people found the following review helpful:
5.0 out of 5 stars
Excellent approach and really insightful,
This review is from: Designing A Data Warehouse: Supporting Customer Relationship Management (Paperback)
If you have to deal with Customer Data Warehouse, this book will save you some precious time and improve your learning curve. It has two main contributions in the project :- Data modeling : provides you tools and hints how to think about data modeling in a "Customer centric data warehouse" - Project management : presents useful tools and business case approach I highly recommend it for anyone involved in a CRM / Data Warehouse project
Share your thoughts with other customers: Create your own review
|
|
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product).
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
