Results 1 to 2 of 2
  1. #1
    Join Date
    Nov 2007

    Unanswered: Pros and cons of having a seperate database for archiving

    Hi all,

    Can someone tell me what would be the best option for archiving, i mean is it better to archive the data into a new database or to the same database. If so could be explain in detail.

    Pros and cons of having a seperate database for archiving

  2. #2
    Join Date
    May 2007
    somewhere in dbforums
    depends upon the amount of data to be archived and how frequently you want to access the data....

    If the amount of data is small and frequently accessed the same can be archived to a separate tablespace on the same database.....

    However if the amount of data is large a separate database is recommended because of the following reasons -
    backups / restore can be done faster for main database
    archives can be maintained in a separate drive, you save on disk space on your main machine
    since the amount of data handled by your main database archival is less, subsequently your maintenance activities gets decreased
    Helps in recovery of archival records if your main database fails [this applies only if you don't maintain periodic backups]

    These are some of them.... maybe someone will add up on those
    Last edited by nick.ncs; 07-10-08 at 02:23.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts