1 / 14

Data Warehouse

Data Warehouse. Ten Common Mistakes By Jon C. Choe. Table of Content. Data Warehousing Institute Ten common mistakes Dr. Paul Dorsey with Dulcian, Inc. Critical success factors for building a Data Warehouse Conclusion. Ten Common Mistakes. 1. Starting with wrong sponsors

marvel
Download Presentation

Data Warehouse

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Warehouse Ten Common Mistakes By Jon C. Choe

  2. Table of Content • Data Warehousing Institute • Ten common mistakes • Dr. Paul Dorsey with Dulcian, Inc. • Critical success factors for building a Data Warehouse • Conclusion

  3. Ten Common Mistakes 1. Starting with wrong sponsors • Data Warehousing Manager • Executive sponsor with great deal of money • Project “driver” • Has already earned the respect of the other executives • Has healthy skepticism about technology • Is decisive but flexible

  4. Ten Common Mistakes 2. Setting unrealistic expectations that can’t be met a. Data warehousing has two phases: Selling Phase – persuade people Struggle Phase –meet the expectation b. Frustrates executives at the moment of truth

  5. Ten Common Mistakes 3. Promoting wrong value of their Data Warehouse a. engaging in politically-naïve behavior a. help managers make better decisions b. lose potential supporters

  6. Ten Common Mistakes 4. Loading Data Warehouse with unnecessary information a. sends a list of table and data elements to the end user along with request b. get back long lists of unnecessary information c. slows responsiveness and increase the data warehouse storage requirements

  7. Ten Common Mistakes 5. Data Warehouse Database Design vs. Transactional Database Design a. Transaction processing: - a programmer develops a query that will be used many times - usually contains only the basic data b. Data warehousing: - an end-user develops the query and may use it only one time - expect to find aggregates – sums, averages, trends, time-series information already calculated for them and ready for immediate display

  8. Ten Common Mistakes 6. Data Warehousing Manager: Technology-oriented rather than User-oriented a. user hostile project manager puts entire project in danger of being scrapped b. Data Warehousing is a service business and not a storage business. c. Don’t make clients angry!!!

  9. Ten Common Mistakes 7. Too much emphasis on traditional internal record-oriented data a. senior executives see data warehouses as irrelevant b. consider including images, graphics, audio or video, etc…

  10. Ten Common Mistakes 8. Delivering data with overlapping and confusing definitions a. Finance manager – sales means net of revenue less returns b. Distribution people – sales means what needs to be delivered c. Sales person – sales means amount committed by clients

  11. Ten Common Mistakes 9. Performance, Capacity, and Scalability a. within 4 month, purchase at least one additional processor equal or larger than the current computer. b. budget for additional hardwares c. budget for unforeseen difficulties d. network overloads are a very common

  12. Ten Common Mistakes 10. Believing that once the Data Warehouse is up and running, your problems are finished a. data warehousing project team needs to maintain high energy over long periods of time. b. Data warehousing is a journey not a destination

  13. Critical Success Factors 1. Project leader must be experienced 2. Careful collection and analysis of user requirements including legacy reports is crucial 3. Get a sence of how users will use the new tool 4. Do a pilot project 5. Make the user happy

  14. Conclusion 1. Data Warehouse projects are different from traditional relational design. 2. Don’t assume that a skilled traditional developer will be able to lead a warehouse project 3. Gather user requirements carefully and completely before building the data warehouse

More Related