Re: How would you guys do this?

What do you expect to set as the situation with concurrency, locks and the like? How much downtime (if any) can you tolerate? Do you have indexed last-update-date/time columns in your transaction tables, which can be used to successively bring the databases into compliance with each other? Have you considered stored procedures as an auto-update mechanism? How about mirroring all disks and then switching the mirroring set over to the new db version and running through upgrade procedures? Do you run Tuxedo or other middleware? More.... MI Melvin A. Ivey, Asst Prof of MIS | voice: 541-885-1346 Oregon Institute of Technology | fax: 541-885-1687 3201 Campus Drive, MS OW143 | http://www.oit.osshe.edu/~iveym Klamath Falls, OR 97601-8801 | The Purpose of Education is *Action* On 27 Apr 1996 Spetc@aol.com wrote: > We are going to move our 5.0 database to another machine running 7.1. > (We will be taking advantage of the extra features such as fragmentation.) > It is approximately 20Gb. > We are a 24 hour operation and wish to do it is as qucikly as possible. > dbexport / dbimport would do it, but that is slow. Is there a quicker way?