Book Review: The Data Warehousing Toolkit 2nd Edition

  • Comments posted to this topic are about the item Book Review: The Data Warehousing Toolkit 2nd Edition

  • I'm curious about how much overalap there is between this book and The Microsoft Data Warehouse Toolkit (

    I have the Microsoft specific one on my desk right now - I'm trying to make the time to read it.

  • I'm currently working my way through this book as we are in the process of building a data warehouse here. So far I have found the book very readable, it's not too dry like a lot of other IT books I have read.


    Hope this helps,


  • I found very little overlap between this book and the Microsoft specific one. The Microsoft specific one assumes you already understand dimensional design - it is focused on implementation using the Microsoft stack.

    I highly recommend the original - especially if new to dimensional design.

    john g

  • The core difference that I've noticed is that The Microsoft Data Warehouse Toolkit approaches the topic of building an end-to-end solution on top of the entire Microsoft BI Stack. However, the text only scratches the surface of "dimensional modeling" per se which is at the core of Kimball's methodology.

    The Data Warehouse Toolkit: The Complete Guide to Dimesional Modeling on the other hand goes into great detail of how to structure a Kimball data warehouse design, and covers how to model "Business Processes" in depth. As stated by the reviewer, this book is database agnostic and, in my view, should be read prior to reading any other Kimball publication. In a nutshell, this is an absolute must read for any DW/BI professional.

  • Great write up. Thanks for taking the time. Your Organizational Culture comment really caught my eye, such as:

    This was so contrary to the corporate culture and belief system that my analysis went straight into the round file.

    There is technical success for a project, which most IT staff tend to focus on, and then there is business success of the project. I am sure your projects were technical successes, but I've found that the business has to want to know the truth. I've found that BI must be sponsored by the business side, and not the technical side.

    Going into a project, if you suspect that the project is not sponsored by the business side, keep it technically sound, but don't be surprised when the truth is ignored. Most organizations need a high level of pain before they will be ready for a change.

    The more you are prepared, the less you need it.

  • David - nice review - and thanks for the mention on MIKE2.0!

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply