How to automatically replicate remote database which is not permanently online

[Uli]

Dear group,

I have to replicate remote data to a SQL Server in the headquarter.
The data are on a site which does not have permanent online-connection
to the headquarter.

I have written a script which replicates the data and i want to set up
a process / batch on the headquarter-machine which roughly does the
following

1) Connect to the remote site
2) start replication script (in fact a stored procedure)
3) on success disconnect from the remote site

All this has to run automatically e.g. during nighttime.

Could someone please outline how i set up the connection and keep it
up during my database-action and how to automatically disconnect after
success of my replication script.

I'd be jolly grateful.

Thanks in advance and Greetings from Vienna

Uli

[Simon Hayes]

"Uli" <ul*********@lycos.at> wrote in message
news:76**************************@posting.google.c om...

Dear group,

I have to replicate remote data to a SQL Server in the headquarter.
The data are on a site which does not have permanent online-connection
to the headquarter.

I have written a script which replicates the data and i want to set up
a process / batch on the headquarter-machine which roughly does the
following

1) Connect to the remote site
2) start replication script (in fact a stored procedure)
3) on success disconnect from the remote site

All this has to run automatically e.g. during nighttime.

Could someone please outline how i set up the connection and keep it
up during my database-action and how to automatically disconnect after
success of my replication script.

I'd be jolly grateful.

Thanks in advance and Greetings from Vienna

Uli

If your only problem is how to connect to the remote site, then it's not
really an MSSQL question but a networking one. An external script or program
will probably be the best solution - you can always make it part of a
scheduled task within MSSQL - but you should get a better answer in a
networking group.

If I misunderstood, and it is an MSSQL issue, then perhaps you can give more
details about your MSSQL version, your replication solution (MSSQL
replication or something home-made) and exactly what you need to do.

Simon