|
|
Posted by Erland Sommarskog on 11/10/64 11:26
NickName (dadada@rock.com) writes:
> Well, if we have only a few or a dozen tables, it won't require tons
> of effort to find data problem for the given situation (database), but
> again, let's say, this db has over 200 tables, checking them by hand
> would seem to be like doing things like Homo Sappiens, I don't mean to
> be lazy, so, how would you systematically at least programmatically
> identify the DRI problems?
I'm afraid that the only answer I give, is the one you don't want to
hear: do it right from the beginning.
And if you didn't do it right from the beginning, you have a nightmare
now to sort out. You can of course set up a unique constraint on the
customer name (just temporarily) and then an FK from accounts to see
what happens, but since it's likely to fail, it's not that useful. You
will have to write SELECTs for all relations you want to check.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|