March 10, 2008 at 12:20 am
Hello,
We are having a data base containing approx 50 tables having total size of 50 MB. These data are replicated from a Server 1 to Server 2 locally through Lan 1. From server 2 we have to replicate only 3 tables (Total 30 MB with daily change of about 10 MB) to a distant server 3 connected in a 2nd LAN through 64 KBPS link . We are using Merge Publication for replication and all our servers are using Windows 2000 server, SQL 2000 version. At first we are replicating data base of Server 2 (Publisher) to distant server 3 (Subscribe) successfully but once we are replicating the daabase of server 1(Publisher) to Server 2 (Subscriber), the distant replication does not take place showing status IDLE, though the replication between Server 1 and 2 is OK.
Please help.
March 10, 2008 at 1:34 pm
What is replication type between your server1 and server2, snapshot, or transactional, or merger? push or pull?
Are your 3 tables among those 50 replicated tables?
March 11, 2008 at 12:03 am
Both the replications from Server 1 to Server 2 and Server 2 to Server 3(Remote) are Merge publication using PUSH option. All the 3 tables which required to be replicated from Server 2 to Server 3 are from the 50 tables being replicated from Server 1 to Server 2. We are changing/adding data in Server 1 only.
March 11, 2008 at 12:34 pm
How many publishers are there? If there is more than one, you may check resolvers, which define what to do when there is any conflict.
March 12, 2008 at 3:35 am
Hmmm...sounds a little confused to me.
Any reason why server 2 cannot be a publisher with two publications.
47 tables in one publication with server 1 as a subscriber
3 tables in one publication with server 1 and 3 and subscribers
Wouldn't that give you a bit more flexibility?
HTH
Graeme
March 12, 2008 at 10:38 am
I was saying you could not. I mean that you may take a look at your resolver settings what actions will take when a conflict occurs.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply