In my October 2001 column, "One Size Does Not Fit All," I wrote about the key steps for rescuing a data warehouse that had gone awry from taking a closer look at ETL tools/processes to the reevaluation of business requirements and organizational processes. This month I’m going to address data warehouse optimization or what I call "reviving the lazy data warehouse."
Recognizing a lazy data warehouse can be difficult. In fact, one key characteristic is that there’s nothing obviously wrong with it. It’s probably doing what it needs to do (loading data, reporting on errors, generating reports). What’s wrong? The business is not seeing any value from it.
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access