July 21, 2011 at 5:54 pm
I have 3 servers (A, B, C).
I have setup up snapshot replication from A to B and B to C (all using snapshot - same database, same table).
I recently had snapshot problem from A to B when B to C is there.
There weren't any problem before I changed the schema of the table that I am replication.
I tried to sync the structure of the table on all 3 serves (I did) and re-add article to snapshot from A to B, that works and then re-add article from B to C, this worked as well.
The problem is when the next day snapshot runs on A and it's saying that the table is used in replication on server B (which is really the case, it is used on B to replicate to C).
How can I make this happen?
July 22, 2011 at 8:19 am
The snapshot does a truncate command. When a table is in replication Truncate is not allowed. Since Server B is also replicating, all the tables in Server B has restrictions. That is you cannot do Truncate command on it.
Why dont you set up snapshot rep-lication from Server A to Server B and C?
-Roy
July 22, 2011 at 11:17 am
Hi Roy,
The issue is fixed. Thank you for your input (very good insight on just replicating from A to B and C - I will need to ask my developer about this). A is under very heavy load already.
on the article level, instead of choosing to drop and create the table, I now use truncate and insert and this solved me problem with snapshot replication.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply