Defensive Database Programming with SQL Server

A couple of weeks ago, I spent some time reviewing a few trigger-based constraints recently put in place to enforce business-rules in a database I’m working on for a client.  Specifically, I was looking for any potential side-effects that could arise with a database that is configured for READ-COMMITTED SNAPSHOT ISOLATION.

During my online research, I stumbled upon a FREE book by Alex Kuznetsov (Blog | Twitter) called Defensive Database Development with SQL Server and found it extremely useful and worth a mention.

click to enlarge

This book is a goldmine of information about issues with which all SQL Server database developers should be familiar…especially Chapter 4 if you’re dealing with snapshot isolation.

  • Chapter 4: When Upgrading Breaks Code
    • Understanding Snapshot Isolation
    • When Snapshot Isolation Breaks Code
    • Trigger behavior in SNAPSHOT mode
    • Building more robust triggers?

In addition to the quality of the material, I found the format to be very effective.  For each topic, Alex explains the issue, covers key considerations and methods for solving, and then goes on to support the information with easy to follow examples.  I’ve only read a few chapters so far, but plan on knocking out the rest over the holidays.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s