Re: database integrity

From: mountain man <hobbit_at_southern_seaweed.com.op>
Date: Fri, 20 May 2005 07:25:42 GMT
Message-ID: <Whgje.8970$E7.702_at_news-server.bigpond.net.au>


"x" <x_at_not-exists.org> wrote in message news:d6i5vu$hgp$1_at_domitilla.aioe.org...
>
> "Tony Andrews" <andrewst_at_onetel.com> wrote in message
> news:1116507337.775726.148290_at_f14g2000cwb.googlegroups.com...
>> mountain man wrote:
>> > Q1: What is database integrity?
>> >
>> > A1: A measure of the self-referential consistency of all
>> > the relations existent between the physical data elements
>> > defined in the schema of a database.
>> >
>> > Any disagreements, improvements, comments?
>
>> So perhaps, and with additional simplifications:
>> A2: A measure of the consistency of the relationships between the data
>> elements defined in a database.
>
> Or (database) integrity is (a measure of ???) consistency (of
> relationships) ?

The dramatic simplification: integrity = consistency seems a reasonable general definition of the term.

> I think it is an all or nothing affair unless you are in the data recovery
> business.
>
> Means to protect database integrity:
> - constraints (normalization, data type, keys, referential integrity,
> etc.)
> - permissions, privileges
> - backups
> - good hardware
> - good software
> - good users
> - good watchdogs
> - good luck
> - plan B

Yes, in the end it is all or nothing.
Good list.

Pete Brown
Falls Creek
Oz
www.mountainman.com.au Received on Fri May 20 2005 - 09:25:42 CEST

Original text of this message