• That's an interesting idea with the NOCHECK constraint. Doing that will allow you to take advantage of 2005s ability to file non conforming ones to a type of UNKNOWN bucket.

    I still would be inclined to leave it on in the beginning and after major changes to catch errors in the transformation and load portion (as I said in a previous post, except for that I would not have caught a load error) although I supposed once committed to the UNKNOW bucket there'd be nothing more to do about it.