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.
Defensive Database Programming with SQL Server Paperback – May 31, 2010
Manning Publications Month of Lunches Series
Check out these featured titles to learn Powershell, Active Directory, and more in a month of lunches.
Frequently Bought Together
Customers Who Bought This Item Also Bought
About the Author
Top Customer Reviews
It really makes you think about the what-if, what happens if your caller does something unexpected and what you might do to mitigate this risk. There are not a whole lot of SQL Server programming books that I learn something from anymore, this was one of them.
Alex deals with this "inconvenient" topic using very practical approach. Instead of filling pages with theory and reasons why defensive programming is good, he dives right into simple examples from the daily work of every database professional. We have all seen (and ignored) many of these issues, but demonstrating how this affects our code and how simple it is to avoid these problems makes this book shine. It is not a complete catalog of defensive techniques, rather a good collection of examples to illustrate the need for defensive coding and applicable methods. It builds the mindset to think proactively and create robust solutions.
The book includes coverage of the following topics: basic defensive technique, code vulnerabilities, changes to database objects, upgrades, reusing code, data integrity and constraints, error handling, concurrency.
"Defensive Database Programming with SQL Server" should be required reading for all SQL practitioners.
This is not a book for beginners that want to learn about T-SQL language, but if you are already familiar with the language then you will learn about best practices for making your program more robust.
Walk with the author through those situations that can make your code to break. Being aware of these situations is a good start, learning how to defend your code from them is what this book is all about.
If you go through the book you will very likely find reference to oversights that you may have made in the past and how to avoid them in the future.
The only negative I can say about the book is that I wish that it had more of the author's helpful hints. A good subject, perhaps, for a Volume 2.
By the way - where did the author get that beautiful cover photo? Where was it taken?