Problem in Multiple Publication on Single Table

Question

 

Hello  Everybody, If any one have solution then please help me.

Thanks in Advance.

I do the following steps:

1. I have created two publications on my SQL SERVER for merge replication
   Publication A – which returns all rows from the Table1
   Publication B – which returns all rows from the Table1 where the field MANAGER =’ABC’
2. I have two clients who have MSDE
   Client 1 is subscribed to Publication A and Client 2 is subscribed to Publication B
3. All works fine till now and I am able to make transfers from the two clients and get all the changed data
4. However, now If I change the filter rules for Publication B and set that it should return all rows from the Table1 where the field MANAGER = ‘DEF’ , SQL Server tells me that I have to reinitialize all snapshots for all subscriptions. If I don’t do this it doesn’t allow me to make a transfer from my Client 1.
   As you can see in my example I have not made any changes to Publication A to which Client 1 is subscribed. So this seems to be illogical.
5. In our case it would not be possible for us to reinitialize the subscriptions for all Publications when the rules for only one Publication are changed because we may have a lot of clients connected to our Server and if we reinitialize the subscription then all the data is sent again.
6. If anybody know that how to restrict the other publications re-initialization then please tell me how we can do.

Answer 1

Hi, Gaurang,

I've tried the scenario you described and got the same result, it seems a bug to me (changing property of one publication should not affect another publication). I will do more research on this issue and let you know if there is a workaround.

Thanks for reporting the problem.

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 2

Hi Zhiqiang

Thank you very much for reply.

If you find any solution then please pass to me.

Gaurang Patel

Answer 3

maybe it's a stupid work-around suggestion, may be not...

 

try1. what happens if you kill publication 2 and then recreate it with your new filter ?

try 2. create a publication 3 with your new filter...

 

HTH, Fabien.

Answer 4

Hi, Gaurang,

The issue is indeed a bug but unfortunately there is no easy workaround at this time. Not sure if Fabien's suggestion will work for you. We will see if it can be fixed in next release or service pack.

Thanks,

Zhiqiang

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 5

Hi Gaurang,

I am from Microsoft Product Support Services. One of my customer also reports the same issue. Currently, our Product Team is checking the issue.

To me, it is much like a bug in the product although we have not got the final confirmation from our Product Team.

We also found that this problem may incur data loss. Consider the following situation:

- Pub A is not synchronized with its subscribers

- You changed the definition of the filter of Pub B

- All the sub is marked as reinitialization thus, you will not have chance to sync pub A.

- Any new data in the sub of pub A is lost.

Thus, for current, please make sure that pub A is sychronized before you begin to modify the filter of pub B.

Sorry for the inconvenience caused.

Thx, -Justin