Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2010

    Unanswered: strategy of a database update

    Dear all,
    I have the following probolem.
    I need to update a database with several thousands users having reading access. My idea is to make separate updated table than to rename old and updated table (this gets the name of the old table) and then to delete old table. Is there any better way to do this.
    Database contains around 20 milions entries 5MB so I need to find an efficient way to update table as fast as possible so without obstructing (as much as it is possible!) reading access. The update depends on the external resources and it is performed in regular time intervals (once per week).
    What is the best practice for this?

  2. #2
    Join Date
    Jun 2004
    Arizona, USA
    Are you updating the data in the table, or are you changing the table design weekly?

    If you're updating the table data weekly, what is the purpose of the update? And, why do you feel the need to go through an elaborate process in this update?

    If you're updating the table design weekly ... WHY?
    "Lisa, in this house, we obey the laws of thermodynamics!" - Homer Simpson
    "I have my standards. They may be low, but I have them!" - Bette Middler
    "It's a book about a Spanish guy named Manual. You should read it." - Dilbert

Posting Permissions

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