A few additions to note.
I’ve been a follower Ralph Kimball‘s articles and books for a few years now. Speaking from my own experience his formalisation of the technique of delivering conformed data marts to build an enterprise-level data warehouse (Bus Architecture) simply works, and works well. I’ve been using it as the basis for a lot of design work over the past eight years, and my most recent client has an extraordinary record of receiving 100% award fees on their contract, based largely (I think) on the rapid development that it enables.
Although proponents of a unified (3NF) Enterprise Data Warehouse have much to say in criticism of it, I haven’t seen any arguments that stand up in practice. They either focus on problems associated with not following proper design procedures (eg. not conforming the dimensions) or on problems that are even less tractable in an EDW/CIF system (having three source systems that give different values for revenue, for example).
I recently finished reading Kimball and Caserta’s Data Warehouse ETL Toolkitbook, which was on the whole a great basis for robust development of the ETL subsystem. Where I did have issues with it was in some database-specific errors (Redo and Undo are notthe same thing) and in what I felt to be insufficient caveats on the differences between feature implementations across different vendors (the ability, or inability, to drop indexes associated with a single table partition for example). However the procedural descriptions and emphasis on the planning and documenting side is beyond reproach, and ought to be required reading for all data warehousers.
On the same lines I have added a link to Intelligent Enterprise, which I like for the less vendor-specific focus on Business Intelligence. Sometimes it does us good to get out for a breath of fresh air.
Lastly, as a fan of extremely long blog posts I have to give a nod to Nuno Souto’s blog, the contents of which speak for themselves. Good stuff, Noons.