SQL Server 2005 Distilled

By Eric L. Brown

Applying the bestselling 'distilled' format, a top SQL Server guru offers a succinct yet authoritative guide to SQL Server 2005. This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0321349792
• ISBN13: 9780321349798
• Release Date: January 2006
• Publisher: Addison-Wesley Professional
• Length: 314 Pages
• Weight: 1.05 lbs.
• Dimensions: 0.6" x 7.4" x 9.2"

Customer Reviews

Executive Summary for SQL Server 2005

If you are an IT manager looking for an "Executive Summary" of the new features of SQL Server 2005, you will love this book! It gives you a nice overview of the new features, what they do, and suggestions for how you might apply them. If your a programmer or a DBA looking for details and examples of how to do things in SQL Server 2005, you need to look elsewhere. My recommendation would be "Pro SQL Server 2005".

How to choose the right tool for the job

This book is perfect for the person who is not well versed in all the new features in SQL Server 2005 and wants to make an educated decision on which features to use for a given situation. I read the whole thing straight through to get my head around all the new stuff but I also noticed that it would be good for someone to just skim through to see if there is anything that would help with an immediate need. It's a lot easier to read this than some 1,000-page tome to decide which features will work for a project; then you can get the 1,000-page tome that focuses on the feature you really need.

Executive Summary - The big picture of SQL 2005

Everybody loves the trees, but some of us need to look at the forest. This book is about the forest. It's for DBAs and IT managers who need to make smart decisions about deployment without getting distracted by the details of implementation. Highly recommended for decision makers. Not recommended for programmers or hands-on DBAs.

A Concise and Valuable Read

A well organized analysis, useful for DBA's, developers and managers alike. Eric Brown neatly documents the strengths and usefulness of new features while explicitly identifying limitations and weaker components. Excellent and thorough summary of the Business Intelligence component including Microsoft's interest in the future of this speciality. By far, my favorite section was "Random Thoughts on Deployment." While the information does not drill down to the granular how-to-code level, sufficient information is contained to direct an interested developer down the path to more specific examples.

2 tiers instead of 3 tiers?!

Microsoft continually improves its SQL Server, and Brown shows how far it has come in the 2005 version. There has been a big push to make SQL Server 2005 industrial strength. So now it can do 1 million transactions per minute, up from 20 000 per minute in 2000. A remarkable gain that suggests Microsoft is making a strong drive into the bread and butter of DB2 and Oracle's customer bases. And, yes, the book comes out in 2006, while the Server is labelled 2005. But it's a very complex product [as the book makes clear], so some slippage was inevitable. Other features covered by Brown include the High Availability, for businesses that need 365/24/7 coverage, or at least as close to this as possible. A very interesting discussion takes place early in the text, where Brown suggests that more business logic needs to be embedded into the database layer, through such means as stored procedures, perhaps. In contradiction to the heavily promoted 3 tier arrangement, of database layer, application layer and presentation layer. Where the application layer holds the business logic. The idea is to separate the latter from depending on a particular choice of database. Brown disagrees. Saying that the performance gains often necessitate pushing the business logic into the database. Maybe. Keep in mind however that every database vendor is likely to say this. Since a major [intended] effect is to lock the customer into that database. With this caveat, Brown might ultimately be correct. For the greatest performance, you may well have to do as the text suggests. Though whether you choose SQL Server or an alternative database is another matter.