The world’s Largest Sharp Brain Virtual Experts Marketplace Just a click Away
Levels Tought:
Elementary,Middle School,High School,College,University,PHD
| Teaching Since: | Apr 2017 |
| Last Sign in: | 103 Weeks Ago, 4 Days Ago |
| Questions Answered: | 4870 |
| Tutorials Posted: | 4863 |
MBA IT, Mater in Science and Technology
Devry
Jul-1996 - Jul-2000
Professor
Devry University
Mar-2010 - Oct-2016
Answer all four questions in attachment.
a. Whatâs the scope of what can be considered a data warehousing failure?
b. What generalizations apply across the cases?
c. What do you find most interesting in the failure stories?
d. Do they provide any insights about how a failure might be avoided?
Data Warehousing FailuresEight studies of data warehousing failures are presented.They were written based on interviewswith people who were associated with the projects.The extent of the failure varies with the organization,but in all cases, the project was at least a disappointment.Read the cases and prepare a one or two page discussion of the following:1.What’s the scope of what can be considered a data warehousing failure?Discuss.2.What generalizations apply across the cases?3.What do you find most interesting in the failure stories?4.Do they provide any insights about how a failure might be avoided?Case Studies of Data Warehousing FailuresAuto GuysAuto Guys initiated a data warehousing project four years ago but it never achieved full usage.Ainitial support for the project eroded, management revisited their motives for the warehouse anddecided to restart the project with a few changes.One reason for the restructuring, according to the projemanager, was the complexity of the model initially employed by Auto Guys.At first, the planner for the data warehouse wanted to use a dimensional model for tabularinformation.But political pressure forced the system’s early use.Consequently, mainframe data waslargely replicated and these tables did not work well with the managed query environment tools that wereacquired.The number of tables and joins, and subsequent catalog growth, prevented Auto Guys from usdata as it was intended in a concise and coherent business format.The project manager also indicated that the larger the data warehouse, the greater the need for higlevel management support – something Auto Guys lacked on their first attempt at setting up the warehouAnother problem mentioned by the project manager was that the technology Auto Guys chose for theproject was relatively new at the time, so it was not accepted and did not garner the confidence that a prousing proven technology would have received.This is a risk inherent in any “cutting edge” technologyadoption.The initial abandonment of the project was undoubtedly hastened by both corporate discomfowith this new technology and the lack of top management support.A short time after dropping the project, top management felt pressure to reestablish it.Because AGuys initially planned an enterprise-wide warehouse, they had considerable computer capacity.It was puto use on a much smaller project that focused exclusively on a single subject area.Other subject areas wedue to be added once the initial subject area project was completed.Auto Guys expects to grow thewarehouse to two terebytes within a year or two and eventually expand to their projected enterprise-widedata warehouse.The biggest difference between pre- and post-resurrection will be that the project willevolve incrementally.Given his experience with the warehouse, the project manager made the following summaryobservations: (1) the management of expectations is critical to any sizeable data warehousing project; (2)proven technology, although not essential, does make the project easier to explain and justify; and (3) thehttps://www.coursehero.com/file/7663758/TUN-DataWarehousingFailures/This study resource wasshared via CourseHero.com
Attachments:
-----------