I usually handle it this way:
1. set the New site to transfer back to the old site (meta tag,
Javascript, CFLocation)
2. Submit the domain change
3. wait several days (a week?)
4. freeze changes to old site
5. Copy old site db to New site
6. test new site
7. Kill transfer from New back to old
8. Set old site to transfer to New site as in step 1
You can set this all up in advance and test it. Then the "down" time
is limited to whatever it takes to do steps 4-8.
Another permutation it to try and synchronize updates to the dbs on
both sites... usually that takes more time and trouble than it is
worth.
HTH
Dick
At 10:28 AM -0500 2/27/01, river wrote:
>Little bit off topic, but I wanted to ask people who uses ColdFusion to
>develop sites with database.
>
>Here is the situation:
>I need to move a site to another hosting. The site has a database and that
>needs to be upgraded from Access to SQL. When the domain registration
>modification takes place, it takes more than a couple of days to propagate
>through the net. So, some people will access the old site that connects to
>the Access database, and some people will access the new one that connects
>to SQL. Consequently, from the time the propagation starts to the time it
>finishes, there will be new data on both the databases.
>
>The integrity of the database is kept on the coding side and not on the
>database side, and I can't simply add the new data on Access to SQL by
>importing.
>
>What would people usually do in this kind of situation?
>
>I appreciate any kind of suggestions/inputs/ideas!
>Thanks in advance.
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
