Developer Forum

I have a set of data that lies within one DB server and I
need to transfer that data to another DB server.

Bassically our application is split up as test and live...
Using Active Server Pages, we initially set up our
customers on our test servers all the data is stored on
the test server DB. Our customers have tested the system
and now wish "Go Live" now we must transfer all the
initial data from the test DB server to the live DB
server. We have a tool wriiten in ASP using ADO to
initailly enter all the data to the test DB server. Now we
would like to extend our ASP application to have a "Go
Live" button witch will transfer all the data....

What is the best practice to this?

Thanks

Anastasios,

You forgot to mention the db involved. sqlserver? oracle? other?
Why not export the data from the testserver and import it in prod. Does this
have to be done through asp/ado because you don't have access to the servers
directly?
If you want good advice you'll need to be a bit more informative.

Regards,
Edwin Kusters

Yeah sorry it's MS SQL Server 2000 and the application is
web bassed ASP 2.x, no fancy .NET stuff...

Bassically we have a web bassed application witch
creates "users" by gathering certain info such as:
username, password, mailling address, contact information
etc... Then the user can use our system and
make "transactions" etc... Eventually when we certify
our "user" we must transfer all the user data and any
additional data required to the "live" system...

The tool that does all the creation is used
by "executives" so it is out of the question to have them
use SQL server directly and the application is ASP web
bassed since we have multiple offices around the world...

Somebody on another news group recomended DTS and use the
COM ibjects with ASP...

other?
in prod. Does this
access to the servers
informative.
message

I
live...
we

nastasios,

I assume both sql server versions (for approval and for life) are able to
communicate with eachother.
In that case you can write a stored procedure that copies the data from one
database to another. You'll need to connect the sqlservers though. There
shouldn't be a need to first move it from a database to a webserver and then
back into another database. That route sounds troublesome to me as it
appears that there are a whole number of tables involved. (the transactions
user enter).

If the activation of a user does not have to be instant there are a bunch of
other options that may be worth looking at. For instance you can mark the
users ready for activation then schedule a job that does an export, move the
data to the other server and have a job there that does the import (with
dts?). Big advantage here is that the executives don't have to wait for the
task to complete with all the possible timeouts you might run into. It will
also prevent a potential bottleneck on your iis server (don't know how much
of an issue that is for you). Because if the copy task is time consuming you
are occupying iis workerthreads and are quickly reducing the overall
throughput of iis.

I do wonder if there is a need to have those database servers seperated. If
you move the data into a single sqlserver (even spread over 2 actual
databases) the solution is much more straightforward and a single job or
stored procedure can do it.

Hope this gives you some ideas,
Edwin Kusters

"Anastasios Angelidis" < XXXX@XXXXX.COM > wrote in message
news:67d101c3582e$f0b50180$ XXXX@XXXXX.COM ...