Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exporting data from one SQL 2K Server to another SQL 2K Server

Status
Not open for further replies.

PiMMeL

Technical User
Sep 29, 2002
43
CA
Hi,

I have a customer that would like to have 1 "master" SQL Server and 3 "Slave" servers.
The goal is to have the 3 "slaves" randomly access/connect to this network and "update" themselves with the data from the "master" server.
Preferrably updates happen only manually with "a press of a button" or a command line or something.

I know a little bit about SQL Server but this is over my head.

Anyone any thoughts?

Thnx Already!!!

Pim
 
Have a look at repliction.
I have a suspicion that you would want transactional replication - the transactions would be held on the distributer until you connect.
If the database isn't too big you could use snapshots.

Another option would be log shipping which would leave read only copies of the database at the lsaves and you would copy and apply all outstanding tr logs on connect.

Another option is t ocode it yourself. Put all updates into tables with an identity column (use triggers or amend SPs. When connect copy all entries from the tables later than the last saved id's and apply.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top