tom@litle.COM (Tom Hampton) (12/13/89)
We are under the impression that Oracle and others make it hard to create a relational environment with active and static parts. You may ask why we would want to do this -- the answer is backups. If we can back up the bulk (8 gigabytes) of our data to tape or WORM and only back up the most recent, active data we have saved ourselves a huge pain in the neck. We also understand that because Ingres works through the UNIX file system, generating an active/statis system with Ingres might be easy with Ingres. -> Can other RDBMS vendors make it easy to have active and static parts? ----- Tom Hampton tom@litle.com Litle & Co. FAX:603 795 2054 P.O. Box 247 Lyme, NH 03768
ben@hobbes.sybase.com (ben ullrich) (12/15/89)
this may be easiest done by dividing up the dataset into seperate databases,
one for static data and one for active data. then you only need to back up the
read/write (active) database, and leave the read-only database alone. i'm not
sure which RDBMS's on the market allow backup of a single database in this
manner, i should think most do. i know sybase does, since each sybase
database on a given sql server is a distinct entity in terms of backup,
recovery, users, and the like. sybase also allows you to mark the static
database 'read only,' disallowing any updates to the database.
..ben
----
ben ullrich consider my words disclaimed,if you consider them at all
sybase, inc., emeryville, ca "When you deal with human beings, a certain
+1 (415) 596 - 3500 amount of nonsense is inevitable." - mike trout
ben@sybase.com {pyramid,pacbell,sun,lll-tis}!sybase!ben