S. Smith said
Be advised that in this book, the author is in a hurry to get to advanced concepts. Only the first three chapters could be called basic. After that, it quickly climbs to advanced material before (in my opinion) sufficiently covering basic and intermediate material. By Chapter 14, the subject is, "Advanced Stored Procedure Programming". But I still can't find what I need in 1-3. Then, as if it is even more advanced, the next subject (Chap 15) is "Debugging". Please, when will we have an author who sees that debugging is a progressively learned process? Perhaps there should be a section in a chapter early on covering debugging of basic stuff.
My background as a programmer of relational databases and writing SQL statements goes back over fifteen years. As my reports and SQL statements have gotten more complex to please the customer, I have had to move into writing stored stored procedures to meet the need for speed. My intent was to get a book that would help me get my SQL statements to work as Stored Procedures. This book appeared to match my customer's software make-up (MS SQL Server, Stored Procedures, .Net, T-SQL, etc) as well as being written in a fairly straightforward and easy to understand manner (it does get a big plus on that!). But if you haven't been writing stored procedures for a year or more, and you have little staff assistance where you are, I would not recommend this book. If on the other hand, you have been doing SP's for a few years or have lots of staff help and want to go the next step, this book may be for you. I'm going to get another one that will help get the basics to work.
Justin du Toit said
I'm finding the book easy to read and understand. Some authors are hopeless, but this one is helpful
Jerome Carolfi said
Like many IT and programming books, this one is no exception in that it seems to be riddled with small errors - things like showing a database schema and then referring to a table by an incorrect name. The most problematic issue with errors like this is that details really matter in these technical fields and it results in a "not ready for prime time" feel to the work. However, if the writer's teaching style appeals to your learning style, then go ahead, because at the end of the day that's what's most important.
Joseph F. Michel said
First off I know the author personally. In spite of that, the book definitely stands solidly on its own merits. This book is shock full of tips, tricks, angles and perspectives to maximize the use of stored procs in your SQL databases. Dejan really goes under the covers to the many aspects of SQL and the reader is the richer for it. This is a very important how to and reference for any serious SQL developer. You will go back to this book again and again. Highly recommended!
Robert P. Beveridge said
Dejan Sunderic, Microsoft SQL Server 2005 Stored Procedure Programming in T-SQL and .NET (McGraw-Hill, 2006)
Not a bad little book, this, though if you've had to dig into SQL2005 for work you're likely to have picked up on a good deal of this already. Still, Sunderic digs down into a number of places where most developers either don't normally have a reason to go or simply fear to tread. You're sure to find things in here you've overlooked (or never thought to look for) unless you're a guru, and even then there might be a [...]bit or two. For someone who just got thrust into "we're upgrading!", it's been great. *** ½
Comments