Virtualizing SQL Server with VMware: Doing IT Right (VMware Press Technology) 1st Edition, Kindle Edition
Use the Amazon App to scan ISBNs and compare prices.
Featured IT certification guides sponsored by Pearson. Learn more.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top Customer Reviews
Page 309 - the high availability chart shows pre-SQL-2012 clustering and SQL-2012+ clustering as having different recovery point objectives. (They don't - they just have different marketing names.) It says database mirroring, AlwaysOn Availability Groups, and failover clusters fail over in less than three seconds - that's just not realistic. It says you can do vMotion on a database mirror - that's not realistic either, because synchronous mirrors often fail over during long vMotions.
Those errors are all on just one page, in one chart, and it just keeps coming.
Page 111 says that if you put your log files on local SSDs, you should "have an additional copy on SAN." That's just not even physically possible with SQL Server - you can have two log files, but if either of them fails, your database is down. This concept is possible in Oracle, and the authors' Oracle background keeps showing up throughout the book. They recommend things that work in Oracle, but not in SQL Server.
Page 111 also says that Microsoft recommends 1 data file per CPU core and .25 to 1 user database. That was true in 2005-2006, but Microsoft has since released multiple knowledge base articles like KB2154845 that have better guidance.
I could go on and on (and in my book review on BrentOzar dot com, I do) but the bottom line is that you should wait for the next revision of this book. The first edition has too many technical problems.
I would have reviewed higher if the book had specified that it is for small, commodity DBs, but as it touts its recommendations for "enterprise" instances, I cannot recommend it. Sorry.
One of the key items I like about a good technical book is the ability to use it not just for learning, but also as a quick reference. This book serves both purposes well.
Overall, this is one of those must-have books in the technical library.