First, the book starts with a pretty thorough coverage of SQL Server. It then gives you an overview of the different ways you can utilize SQL server from .NET. It talks some about Windows applications, some about ASP for Internet and closes with XML and Web Services.
Personally, I thought the SQL coverage was really good - including security and stored procedures, but that the VB.Net coverage didn't provide as much detail as I had hoped.
The main reason I bought this was to try to find some answers to holes I felt other authors had left - deployment strategies and examples (including the SQL portion), dealing with text and binary objects and maximizing application performance. These topics were covered very lightly or not at all in this book.
I also thought the author spent too much time on details that aren't really useful. Its pretty interesting that you can modify table structures on the fly, but how many production applications actually do that? I would have appreciated much more time on reading and updating data than all of the stuff surrounding manipulating the schema. My normal mode of operation is to modify the table in the Enterprise manager and let it generate a SQL script for me to build the database. I don't plan on writing programs to modify the database structure; I'd rather program to modify its contents. He also spends a chapter on views from SQL, but views aren't used in any VB code anywhere in the book.
My final criticism is this - the SQL material and VB material are too separate. For instance, he spends a lot of time on stored procedures and their power. He mentions some of the ways they can be used in VB. That would have been a great time to show VB and utilize the procedures he just developed. Instead, the utilization happens about 200+ pages later. I think the author could have developed a great book, but instead we just got a good one.
Here's the summary - it is a thorough treatment of SQL. If you're looking to understand SQL Server there is a lot of good material here (a little too much sometimes, but I'd rather have that than fall short). You will learn all about views, stored procedures, user defined functions and even security. This stuff makes it worth the price of the book. But if you are looking to figure out how to develop for SQL Server from VB.NET, there are better books - try ADO.NET Step by Step instead or Beginning Visual Basic .NET Databases. In the mean time, I'm going to keep looking for something that answers my specific questions better.