Data Constraints Vs Application Constraints
Date: 9 Mar 2005 05:05:34 -0800
Message-ID: <d547331b.0503090505.12448557_at_posting.google.com>
Dear All,
I have just started work at a new company as a 'Data Solutions Architect', and am now patently aware why they need someone with Data Architecture experience.
There databases (be they Oracle or SQL Server etc) have no constraints other than Primary Keys (thank Codd, for small mercies) i.e. all 'relationships' are handled/enforced by the application.
I am in the middle of proposing that as a 'first step', before I look at data integration etc that the integrity of the data should be enforced at the DB level as well as at the application level. Now the business arguements, to them will I imagine look pretty weak at first i.e. the systems working fine, without errors etc, so we don't need another overhead.
As a consequence I am compiling a list of arguements for enforcing data integrity within the database (as well as within the app) and would be interested in anyone's opinions and/or experiences within a similar situation, and what they found to be the key arguements which won the business round.
All thoughts, opinions, arguements, musings welcomed.
Regards
G
P.S. we're not talking about a small company either.... Received on Wed Mar 09 2005 - 14:05:34 CET