An A for DRI in Chapter 2

When I first started this chapter I was sure this would be the standard database design do’s and don’ts, make sure you have PK’s, FK’s, and yada yada yada.

The chapter grabbed my attention right out of the gate when the author clearly spelled out that he understands what I see every day. There is a big difference between book theory and what works in production, but when Louis completes the line between what I work with every day and what is the right or wrong way he has my attention.

Louis does a great job starting off explaining why it is so important to start from the very basics, Your data integrity starts with the column design. Don’t be caught as the DBA where 6 months after you release your design into production saying my, “data integrity blows.”

If you have had a doubt as to why or when you should use constraints, triggers or other data integrity methods you cannot be without this chapter. If you are sure you know where to use each of these it can’t hurt to read up and validate your designs.


0 Responses to “An A for DRI in Chapter 2”

  1. Leave a Comment

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 11 other followers