HP3000-L Archives

May 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Wed, 14 May 1997 14:06:17 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
[...previous answers snipped...]

Here's another way of looking at a true RDBMS vs
Indexed/Networked/Heirarchical database models:

With IMAGE, you can have all of your internal pointers, indexes, and
other "relational" information completely hosed by a catastrophic
failure and you can fully recreate the database from the raw data (well,
with the exception of the bitmaps that show active/free status of
records within a block).

With an RDBMS, the data is scattered around everywhere, and many
"tables" (depending on the specific software) are simply pointers to
the data and not "duplicates" of the data itself (as in Image "keys"
actually duplicating in each affected dataset).  Lose your pointers here
and pray you have a recent backup.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2