December 23, 2004 at 10:51 am
Hi All,
I am looking for ways to replicate some data.
I have many client DB's across the WAN which spans the whole UK and them some.
What we are looking to do is start running AS a DB in our office.
Now, Every night I need to connect to each client DB (VPN's are existing and connections are semi stable) and pull down all the changed data. Changed being new rows. Very little of what I need will be updates.
To use Snapshot replication is not ideal as far as I can see. It's gonna be slow. and wil move a lot of unessasary data. i.e. Rows that are already here.
I've been looking into using MSMQ to move files from client (DTS Out / compress) to us and load them back in. Problem with this is there is another layer (My app to push and again pull the files) from MSMQ ba ck into SQL.
Does anyone know of a nice way to accomplish this?
Biggest thing is reliability. Due to sometimes unstable connections, it need to be able to handle dips in connection, some _very_ slow connections as well as if 100 new rows appeared, I need to be certain that 100 rows ended up my side.
How reliable would DTS Data Pump, commit every 1 record, ignore duplicates be? Anyone tried this? A bit dirty though.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
December 23, 2004 at 7:21 pm
December 24, 2004 at 1:51 am
I have tried this on a client's machine and it's to slow. I assume this is due to the latancy between us and client.
Although, I could use transactional replication from their DB onto another DB on the same server. then use snap shot between that DB and us. Bit of a round about way.
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply