Re: Backup & Restore Granularity

Matt Bentley (mbentley@xmission.com) wrote: : In article <32E8C9E4.167E@genacc-us.com>, : Paul Reimold <preimold@genacc-us.com> wrote: : >I am fairly new to Informix admin. I was surprised (and disappointed) to : >learn that On-Tape, On-Archive (and, I believe the up-coming On-Bar) : >back up and restore only at the dbspace level. WHY NOT AT THE TABLE : >LEVEL? : > Table level backups would be nice, but it could create problems with database integrity. Suppose you had two tables that relate to each other. If you restore one and not the other (at the same time), your data would be out of sync and it would wreck havoc with a relational model. Actually I'm surprised that Informix lets us do dbspace level backups. One of my loves/hates with Informix is that the products are very paternalistic... they don't let you do things that will compromise your relational model, even if you know what you're doing and you really do want to compromise it. : >If a user is in dbaccess, it is frightlenly easy to drop a table. : >Indeed, the term 'drop' implies to me that one simply does not want to : >work with a table any more, not the more serious action of blowing it : >away! : > : >Other than assigning a dbspace to each table, is there any other way to : >backup/restore individual tables? : > : Don't grant DBA to users and they can't drop a table. : We put our large tables in their own dbspace. The smaller tables will go in a : single dbspace. Then we will unload the smaller tables regularly(weekly, : daily) just in case I drop the table or the user deletes everything in the : table. : Matt Bentley : mbentley@xmission.com -- --------------------------------------------------------------------------- Joe Lumbley(jlumbley@netcom.com) ---------------------------------------------------------------------------