The purpose of this series was to give you some basic queries that I use to provide me with a quick snapshot of how well tuned an EDW is from a workload analysis and database tuning perspective.

The four topics were (direct links are provided at the end of the article):

  • Part 1 - Excessive Use of String Manipulation Verbs
  • Part 2 - Analyze Secondary Index Usage
  • Part 3 - Statistics Analysis
  • Part 4 - Compression Analysis

Have you tried them yet??

As a developer or DBA at your site, you have spent countless hours (or years) working on building the best EDW that you can. You rightly should be proud of your accomplishments and the business benefits you are delivering to your customers and/or end users.

However, now that you have the queries, I want you to take a step back and take a holistic look at what is actually implemented. Fact over perception. This means it is time to play “consultant” for your company!

Pretend that you have just walked into your site, and you want to get a "feel" for how this particular EDW is implemented and tuned. Run the four analysis queries, and objectively look at the results.

What do they tell you? What areas might be lacking or need to be further looked at? Is compression and tuning being applied as well as you would like? How does the query workload look – is it begging for model changes or education? Use the results to focus in on and plan corrections.

I also like to run these queries occasionally in the development and test environments of my clients. It is a quick little double check that something isn’t being missed as tables and query / etl workloads move through the development stream. Much better to catch issues then, rather than after implementation.

Try the process out at your site and see what you get. If you can, please share some feedback on your results with the rest of us. Here are the links to all four topics:

As always, comments or questions are welcome.

Good Luck!