SQL Server MVP: Deep Dives [ペーパーバック]

I bought this book for full price at the SQL PASS conference in 2009 and I didn't even feel bad about paying full price because of the cause. After reading through a number of the chapters, I still don't feel bad for paying full price :-)

This book contains 59 golden nuggets. You name the topic and there is likely a white paper quality or beyond chapter for your interest. From Database Design, to development best practices to complex administrative or BI issues, it covers it.

I could not put the book down on my flights back and still have managed to find the time to leaf throw more. I will be suggesting all of the developers and system administrators (part reluctant DBA) purchase their own copy (primarily because I don't want to share my copy :-P) and get learning.

Some great approaches to common problems, some great forays into areas I have, unfortunately, not forced myself to get into (like Power Shell for my administrative tasks). I will be taking some of the tips, like the Tools database and Aaron Bertrand's version of a great utility script to easily show the important info on active tasks, and putting them to use as early as I find the time next week.

I am also going to force my SSIS developers to read Andy Leonard's chapter on Incremental loads and other SSIS chapters while re-reading Erin Welker's chapter on BI For the relational guy (that's me) a few times myself.

Every chapter is top quality and I really liked the in depth approach. This is a good reference to add to a library with some of the great internals books or in depth books on a single topic. Also nice knowing that these top notch MVPs, mostly all great speakers and authors, gave up their time and royalties to give to a worthy cause.

Wow! Actually this could be the whole review, but I guess it does need some elaboration. This book is bound to become a classic just like Ken England's book on performance of SQL 2000 used to be, or the Inside Microsoft SQL Server series is now.

It does not happen that often that I keep postponing all but the pressing task at work to read yet another chapter. Can someone be called an SQL addict? This book may well make you one. So I've tried to get to the bottom of it and understand what is it that they have done so right. It is not only that the book is written by people who know what they are writing about, and that they display the essence of various topics which most of us have accumulated only through reading many other sources. Here it is all distilled and presented in one single volume of 59 chapters. But more than that, it seems that they have found the ultimate golden ratio in the size of the chapters, roughly between 8 to 13 pages, so that each can be covered in one short read without distraction. Almost like reading a collection of short stories by Edgar Allan Poe or William Somerset Maugham.

Have you ever spent time going through the 1204 trace flag deadlock graphs and then made the transition to the new trace flag 1222? Here it is, explained clearly without the need to go to BOL or the web. The benefits of a covering index? Which DMVs to use? Even the absurdity of using a shrink database task in a maintenance plan (why do they offer such a thing in the first place?). It is all here. The range of topics is impressive.

I have to admit I have not read more than a seventh of the book (only got it two days ago), jumping from one topic to another, having to balance what I am interested in most, and what would immediately be applicable to my current work, but even without a FULLSCAN there is little doubt that this volume will be enthusiastically received by developers and DBAs across the globe.

This is like a dream book. The best, most knowledgeable, and helpful, SQL Server experts each get to pick a topic of their own and write about it. Things gets better. The book then gets edited by some of the great names in SQL Server over the last 10 years (and more). But, do these fantastic people stop there? No. They go on and write the whole book for charity. All the author royalties are going to support War Child International. Over the years, I've read books and articles by many of these people. I've also attended classes or conference sessions presented by them. I've even had the opportunity and privilege of talking to quite a few them both online and in person. These people are not only well versed in SQL Server technology, but they're nice, funny, and friendly people.

Enough about them, let's talk about the book. There are 59 different chapters, written by one or more of the MVP's involved with the book. The chapters are broken down into five different sections; Database Design and Architecture, Database Development, Database Administration, Performance Tuning and Optimization, and Business Intelligence. In other words, something for everyone.

You probably should sit and read this book cover to cover, straight through, but I've found myself jumping from one topic to another. For example, Joe Webb's chapter on indexes and column order was immediately useful. Like all the chapters, it's direct and clear, with some good sample code, a few screen captures and a great explanation of the concepts that it's going after. Lots of people will benefit from Gail Shaw's description of how to trace deadlocks. But then I had to jump right back to Chapter 1 and read Louis Davidson & Paul Nielsen's chapter on relational design ideas. It's hard to settle on a single topic. Michael Coles has two chapters on XML, both are worth a read, especially if you're moving from SQL Server 2000 into 2005/2008 where you can begin to put XQuery to work instead of using OPENXML. It just goes on and on, your favorite MVP's from all around the world writing on hand-picked topics, edited by experts in the field.

The printing itself is very well done. The seperation between the text, code and notes is very clear. The graphics are also clearly printed and very readable. The binding seems very well done. It's held up well to my initial, constant, thumbing from one article to another.

Taken as a whole, tons of experts covering a huge swath of information in a very well put together book that benefits an imminently worthy charity... Why are you still reading this? Get a copy and see how it can improve your own system, your own designs, your own code, and feel good knowing purchasing the book helps not just you and your organization, but other people all over the world, kids.