1) You could prevent updates/deletes to the old (Access database)
OR
2) You could have the new hosting and database setup and have the old
website access it as a remote datasource (via IP)
> Little bit off topic, but I wanted to ask people who uses ColdFusion to
> develop sites with database.
>
: Domain Move and Data Integrity
> Couldn't you just point the DSN on the access side to the SQL
> db until the
> change takes place?
I've got a similar problem.
A site is in on a server at IP address 123.0.0.10 (for example).
You move the site to a different server (at t
The problem you described below would not occur if you set the server on
the old address to access the datasource on the new address. Two sites
yes, but only one datasource.
> > Couldn't you just point the DSN on the access side to the SQL
> > db until the
> > change takes place?
>
>
> I've go
> This is one of the prime reasons not to use an Access or file-based
> database. If you use SQL Server, or any client server DB, you simply point
> the new DSN to the new SQL server. Both sites can now use the same
> database. No hassles. No updates. No "merging" of data.
Here's a few other "
ght for "some"
things...
Aaron Johnson, MCSE, MCP+I
Allaire Certified ColdFusion Developer
MINDSEYE, Inc.
617.350.0339
617.350.8884
66172567
[EMAIL PROTECTED]
-Original Message-
From: Aidan Whitehall [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 12:39 PM
> Couldn't you just point the DSN on the access side to the SQL
> db until the
> change takes place?
I've got a similar problem.
A site is in on a server at IP address 123.0.0.10 (for example).
You move the site to a different server (at the same host or not - doesn't
make a difference) on I
River,
We just went through this situation. The previous comments are right on.
1) Point the old site to the new database at the new hosting company (you
can do this with the IP of the new hosting company)
2) Have the old hosting site re-direct the IP address to the new hosting
site (when you a
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
Couldn't you just point the DSN on the access side to the SQL db until the
change takes place?
Jay Patton
Web Design / Application Design
Web Pro USA
406.549.3337 ext. 203
1.888.5WEBPRO
www.webpro-usa.com
- Original Message -
From: "river" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECT
How about a re-direct to the new site's IP address for awhile until the dns
is only hitting the new site. That way, all users will be using the SQL
database instead of the Access one.
David Schmidt, ACP
-Original Message-
From: river [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February
What I meant to say is http refer the old site to the new ip address - which
should be live before the DNS updates happen.
J
-Original Message-
From: river [mailto:[EMAIL PROTECTED]]
Sent: 27 February 2001 15:29
To: CF-Talk
Subject: Domain Move and Data Integrity
Little bit off topic,
place a http refer on the old site to redirect everyone to the new site and
only update the new one!
J
"You're a big man, but you're out of shape. With me it's a full time job.
Now behave yourself."
"Get Carter" 1964
-Original Message-
From: river [mai
12 matches
Mail list logo
