I disagree with the first reviewer of this book. I think the reason for that is what he focused on.
"Refactoring" by Martin Fowler suffers from the same problem. The value in this book does not lie in the refactorings themselves. The value lies in the 100+ pages at the front of the book where the process and environment needed to refactor databases is described.
After having read these few chapters, a lot of people I have talked to are left with a feeling of having read a lot of ideas that should have been obvious from the word go. Yet, not a single one of them were able to come up with these ideas by themselves. That is where the real value of this book lies. This is not a blueprint book which teaches you how to go about refactoring database schemas. This book teaches how to remove the obstacles that make such refactorings impossible.
I think books which state the obvious ideas people don't seem able to dream up by themselves are the most valuable. Therefore I think this book warrants four stars.
10 people found this helpful.
Was this review helpful to you?