Home > Store

Impossible Data Warehouse Situations: Solutions from the Experts

Register your product to gain access to bonus material or receive a coupon.

Impossible Data Warehouse Situations: Solutions from the Experts

Book

  • Sorry, this book is no longer in print.
Not for Sale

Description

  • Copyright 2003
  • Dimensions: 7-3/8" x 9-1/4"
  • Pages: 432
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-76033-9
  • ISBN-13: 978-0-201-76033-0

This book takes a unique approach to the problems faced by data warehouse professionals. The author and the contributors have gathered over 90 situations that they have been asked about in their seminars and presentations, that they have faced in their own work, and that have been submitted to the very popular "Ask the Experts" forum at DMReview. These are all real situations, but they have been disguised to protect the guilty. Topics covered include staffing, budgeting, security, vendors, architecture, and data quality. Each of the "impossible" situations will have one or more solutions contributed by the expert panel. Their different answers and viewpoints, especially when they disagree with one another, provide enlightening reading, as well as useful ideas. This approach should appeal to a broad range of people involved in all aspects of Data Warehouses.

Sample Content

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 1

Table of Contents

(NOTE: Each chapter begins with an Overview.)

Credits.

I IMPOSSIBLE MANAGEMENT SITUATIONS.

1. Management Issues.

The Data Warehouse Has a Record of Failure.

IT Is Unresponsive.

Management Constantly Changes.

IT Is the Assassin.

The Pilot Must Be Perfect.

User Departments Don't Want to Share Data.

Senior Management Doesn't Know What the Data Warehouse Team Does.

2. Changing Requirements and Objectives.

The Operational System Is Changing.

The Source System Constantly Changes.

The Data Warehouse Vision Has Become Blurred.

The Objectives Are Misunderstood.

The Prototype Becomes Production.

Management Doesn't Recognize the Success of the Data Warehouse Project.

3. Justification and Budget.

User Productivity Justification Is Not Allowed.

How Can the Company Identify Infrastructure Benefits?

Does a Retailer Need a Data Warehouse?

How Can Costs Be Allocated Fairly?

Historical Data Must Be Justified.

No Money Exists for a Prototype.

4. Organization and Staffing.

To Whom Should the Data Warehouse Team Report?

The Organization Uses Matrix Management.

The Project Has No Consistent Business Sponsor.

Should a Line of Business Build Its Own Data Mart?

The Project Has No Dedicated Staff.

The Project Manager Has Baggage.

No One Wants to Work for the Company.

The Organization Is Not Ready for a Data Warehouse.

5. User Issues.

The Users Want It Now.

The Business Does Not Support the Project.

Web-Based Implementation Doesn't Impress the Users.

Management Rejects Multidimensional Tools as Being Too Complex.

The Users Have High Data Quality Expectations.

The Users Don't Know What They Want.

6. Team Issues.

A Heat-Seeking Employee Threatens the Project.

Management Assigned Dysfunctional Team Members to the Data Warehouse Project.

Management Requires Team Consensus.

Prima Donnas on the Team Create Dissension.

Team Members Aren't Honest about Progress on Assignments.

A Consultant Offers to Come to the Rescue.

The Consultants Are Running the Show.

The Contractors Have Fled.

Knowledge Transfer Is Not Happening.

How Can Data Warehouse Managers Best Use Consultants?

Management Wants to Outsource the Data Warehouse Activities.

7. Project Planning and Scheduling.

Management Requires Substantiation of Estimates.

IT Management Sets Unrealistic Deadlines.

The Sponsor Changes the Scope But Doesn't Want to Change the Schedule.

The Users Want the First Data Warehouse Delivery to Include Everything.

The Project Manager Severely Underestimates the Schedule.

II. IMPOSSIBLE TECHNICAL SITUATIONS.

8. Data Warehouse Standards.

The Organization Has No Experience with Methodologies.

Database Administration Standards Are Inappropriate for the Data Warehouse.

The Employees Misuse Data Warehouse Terminology.

It's All Data Mining.

A Multinational Company Needs to Build a Business Intelligence Environment.

9. Tools and Vendors.

What Are the Best Practices for Writing a Request for Proposals?

The Users Don't Like the Query and Reporting Tool.

OO Is the Answer (But What's the Question?).

IT Has Already Chosen the Tool.

Will the Tools Perform Well?

The Vendor Has Undue Influence.

The Rejected Vendor Doesn't Understand "No".

The Vendor's Acquiring Company Provides Poor Support.

10. Ten Security.

The Data Warehouse Has No Security Plan.

Responsibility for Security Must Be Established.

Where Should a New Security Administrator Start?

11. Eleven Data Quality.

How Should Sampling Be Applied to Data Quality?

Redundant Data Needs to Be Eliminated.

Management Underestimated the Amount of Dirty Data.

Management Doesn't Recognize the Value of Data Quality.

The Data Warehouse Architect Is Obsessed with Data Quality.

The ETL Process Partially Fails.

Source Data Errors Cause Massive Updates.

12. Integration.

Multiple Source Systems Require Major Data Integration.

The Enterprise Model Is Delaying Progress.

Should a Company Decentralize?

The Business Sponsor Wants Real-Time Customer Updates.

The Company Doesn't Want Stovepipe Systems.

Reports from the Data Warehouse and Operational Systems Don't Match.

Should the Data Warehouse Team Fix an Inadequate Operational System?

13. Data Warehouse Architecture.

The Data Warehouse Architecture Is Inadequate.

Stovepipes Are Impeding Integration.

Should Backdated Transactions Change Values in the Data Warehouse?

A Click-Stream Data Warehouse Will Be Huge.

Time-Variant Analysis Requires Special Designs.

Management Wants to Develop a Data Warehouse Simultaneously with a New Operational System.

The Data Warehouse Gets Assigned the Role of a Reporting System.

Meta Data Needs to Be Integrated Across Multiple Products.

How Can UPC Code Changes Be Reconciled?

14. Performance.

The Software Does Not Perform Properly.

The Data Warehouse Grows Faster Than the Source Data.

Loading the Fact Table Takes Too Long.

Appendix A: Data Warehouse Glossary.
Appendix B: Colloquialism Glossary.
Bibliography.
Experts' Bios.
Index. 0201760339T09112002.

Preface

In the seminars, presentations and classes we teach on data warehouse, we are often subjected to what appear to be “Impossible Situations.” Likewise, on the DMReview “Ask the Experts” forum (reference www.dmreview.com) we are confronted with questions that, at first glance, appear to have no answers or solutions. They do have solutions and that’s what this book is all about.

The 91 Impossible Situations in this book were taken from our classes, from the DMReview “Ask the Expert” forum, from data warehouse consultants and colleagues in the field who have experienced these situations. These are all real situations but they have been disguised and sanitized to protect the authors as well as to protect the organizations experiencing the situations from the attendant shame and humiliation. As a side note, as the situations were disseminated, reviewers were quick to say, “I know what company this describes,” and they were almost always wrong.

Purpose of This Book

There is no reason that each organization, as it begins and continues to develop data warehouse projects, must wrestle with many of the very difficult situations that have confounded other organizations. The same impossible situations continue to raise their ugly heads, often with surprisingly little relation to the industry, the size of the organization, or the makeup of the organizational structure. This book is, first of all, to let you know you are not alone and your problems are not unique. The book should give hope to the perplexed who see no obvious solution to their problems.

Some of the situations should resonate with those of you planning to enhance your data warehouse, to add new data, additional users, and new applications. It may be that the impossible situation has not yet emerged, but you definitely see it just around the bend. This means that you should be able to avoid the situation rather than having it develop and then needing to fix it.

Who Should Read This Book

Every stakeholder, data warehouse architect, data warehouse project manager, and user liaison responsible for any portion of the data warehouse will be faced with the challenges identified in these pages. These people are looking for solutions to situations that, at first, appear to have no answer and appear to be impossible.

This is not an introduction to data warehouse. Readers should have some level of familiarity with data warehouse either through practical experience, conferences, or previous reading of data warehouse texts. This book is also not geared to any primary topic such as meta data or data quality but covers a broad range of areas. The reference section has both introductory as well as more advanced suggested reading material.

User liaisons and managers may only be interested in and want to read Section I, Impossible Managerial Situations.

How This Book is Organized

The first part of the book deals with managerial situations and the second part with technical situations. The order within these sections is very roughly the order in which projects are developed and situations are encountered but the sections are not dependent on each other. The book can be read from front to back but more likely, the readers will be drawn to the sections that cause them the most pain. For example, if the reader is struggling with data quality issues, Section 11, Data Quality, would be the place to start. The order of the answers is alphabetical by the experts’ last name.

A technical glossary at the back of the book should clarify some terms and will also keep the reader from going down the wrong path. Terminology misunderstanding in this fast-changing field has caused significant misinterpretation that has resulted in wasted time and money, dissension and hurt feelings. The glossary contains acronyms and data warehouse and IT terminology. There will be a few cases with more than one definition. Please refer to the definitions to avoid any misunderstandings on your part. Those whose native language is not English will find the Colloquial Glossary useful since the experts were fond of using colloquial expressions.

The reader will notice strong biases in the experts’ responses. The experts came to these dearly held opinions honestly through extensive experience in real world situations. The reader will also quickly realize that some of the answers are in sharp disagreement and appear to be contradictory while a few are embarrassingly similar. The editor made no attempt to reconcile the differences. Recognizing that there is usually more than one answer, very much depending on the organization and the situation, the different approaches have been maintained. Any reconciliation or choice of approach is left to the reader who, we assume, is astute enough to find the relevant answer and pick the solution that will work in his or her organization.

The Experts

Sid Adelman
Joyce Bischoff
Jill Dyche
Douglas Hackney
Sean Ivoghli
Chuck Kelley
David Marco
Larissa Moss
Clay Rehm

The experts represented in this book are all real experts in data warehouse. They have been working in the data warehouse arena for a cumulative 130 (+12) years. If anyone can address these impossible situations, they can.

The experts have suggested best practices based on their experiences with both successful and unsuccessful implementations. The experts correctly identified many of the situations as reflecting the symptoms of a dysfunctional organization, knowing that without understanding the real causes, no effective solution could be honestly recommended. The experts resorted to making assumptions about the situations when not enough information was provided.

The experts’ bios are in the Appendix.

Follow-on

There were a number of impossible situations that came in after the original batch of 91 were sent to the experts and we all feel sure more will appear. If you have a situation you would like to contribute, please send it to impossibles@sidadelman.com. If there is to be a second edition, your situation may be included.



0201760339P05212002

Index

Click below to download the Index file related to this title:
Index

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020