Posted by Erland Sommarskog on 11/23/07 22:18

Fritz Franz (fritzfranz24@hotmail.com) writes:
> OK, I understand. Yes, you ar right, the design of DB is not normalized
> correctly. But for some reasons we decided to do it this way. It is not
> that important to have the FK defined in the DB, the applications will
> ensure the integrity of the data.

An application cannot ensure data integrity. An application can add its
own checks, and sometimes it has to make messages user-friendly. But it
cannot ensure data integrity, because sooner or later someone will run
an UPDATE/INSERT/DELETE directly from SQL when the application is not
watching.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: SQL Express - Identity specification property - how to change
• Prev in forum: Re: Concat instead of SUM when grouping results
• Thread view: Re: foreign keys - on which kind of keys do the base on?

[Reply to this message]