relational databases

This book is great. It's loaded with recommendations that I have not seen in other SQL books and I've read at least a dozen of them. Even the backup modules cover more information than anything I've seen. Every DBA should read this and stop complaining about this or that not being covered. If you looking for replication than find a replication book. It's impossible to cover everything about availability in one shot and this one comes close.
Great stuff!!!

I got this one to help me with setting up a HA replication arch. To be nice about it the repl info in the book is anemic. Next to nothing about it. I'm not sure how I will use the book and Im pretty disappointed iwth it.

I had to say something here. Everyone got so used to everything being easy in windows, they don't want to hear about also having to know what their doing. Do you think running big available db's is a step-by-step process that Bill left out of the books online? One book can't teach you a college degree worth of information.

This book was right on track and the cluster and log ship info just isn't anywhere else. I agree replication was light, but who runs repl for availability anyway? The book put some humor into a grim subject, so it comes across not so serious, but at least it wasn't boring or a reprint of books online. The last chapter had monitoring info you can't get anywhere else, and it was worth the price of the book. Take a look at the cd, there's some kick-A stuff on it, like what looks like another chapter on performance issues effecting uptime.

What some of you guys write here and in thse newsgroups just proves that Bill's worse problems are not in his software. If you're serious about software, you keep up with it. If Microsoft saw some use in trying to get the word out by printing a late book on sql and getting some big name writers to do it, then I'm reading it. Are you going to ignore it because of some guy off the internet? Remember we're talking availability here, so its not the million dollar question.

I'm giving the book four stars. It skimmed over some things it should of covered (like performance, operations, qa testing, handling heterogenous systems, and some other stuff) and it should be a series of books, not just one huge one. It wouldn't hurt if they could referenced non-microsoft books for some subjects that aren't software. Plus it should have more on running high availability systems without clustering or fancy hardware. Only some databases that have to be up all the time run on Enterprise Edition. But everyone will blame Bill if their system is down. Don't they know that by now?