When our data warehouse went into production about 8 months ago, we never had any problems. Now, everybody loves the data warehouse, but they don't love the long wait for responses to their queries. What are we doing wrong?
Sid Adelman's Answer: Your mistake is typical of most organizations that have a successful data warehouse that everyone loves (they won't love it for long when all you can give them is long response time).
You should have anticipated the increased volume and been sure you had the hardware, network and the data base design to be able to support all the new people who love your data warehouse. Even more important, you need a process to monitor response time, resource usage and be able to identify queries that suck up cycles and I/Os. You want to be proactive and not wait until the users complain about response time.
You will need to take appropriate actions to improve response time. The actions may include reconfiguring the disk, changing the RDBMS parameters, establishing indexes, building summary tables, tuning the data base, redesigning the data base, buying a larger CPU, or installing more network bandwidth. Understand that without being able to monitor, you will never be able to know what actions to take.
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