Re: onarchive question

Debbie Shelton (shelton@entropy.krldwa.mccaw.com) wrote: : In article 958@clarknet.clark.net, miriam@clark.net (satori..MSLO) writes: : > does anybody out on the net know if i can restore to the table level : > using on archive.. : > i know i can restore on t he dbspace level in ontape..but we need to beable : > to recove just a singe table from a database.. and not recovve all the : > database in one dbspace. : > : > thanks : > : > miriam@clarknet.com : > : If you set up your tables such that they are all in their own dbspaces you shouldn't : have any problem recovering one particular table. Your database and tables within : the database don't have to all go into one dbspace. Create multiple dbspaces, : possibly one per table (If that's what you want/need) and you'll be set. : -Debbie Shelton : DBA : McCaw Cellular Communications, Inc. : debbie.shelton@mccaw.com Point taken, but in a large environment, where there are actually 10,000 or more tables, and you do want to have the ability to restore at the table level, your proposal falls apart for 2 reasons: 1. The limit for number of dbspaces is 2K. 2. No sane person could administer 2048 dbspaces, especially in a dynamic environment. I hope that reinforces the idea that a logical level **archiving** tool is needed in addition to the disaster recovery backup tools like ontape and onarchive (mis-named, should be onbackup!). -- ========================== standard disclaimers apply ======================== Michael T. Reed, DBA, HCIA, Inc. "A database is like a lake. Efforts 24 Frank Lloyd Wright Drive to clean the lake yield short term P.O. Box 303 results. In contrast, eliminating Ann Arbor, MI 48106-0303 sources of pollution, while slower, tel. 313-930-7943 fax 313-769-6544 yields lasting benefits." T.C. Redman email mreed@hcia.com