Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!ames!pasteur!ucbvax!mtxinu!sybase!hobbes!ben
From: ben@hobbes.sybase.com (ben ullrich)
Newsgroups: comp.databases
Subject: Re: Relational Databases with static portions?
Message-ID: <7538@sybase.sybase.com>
Date: 14 Dec 89 16:02:49 GMT
References: <629551370.tom@litle.COM>
Sender: news@sybase.sybase.com
Organization: sybase, inc., emeryville, ca
Lines: 15

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