Merge replication columns limit?

Hi,

I am experiencing a wired problem withe merge replication and SQL 2000 SP4.

We had replication working for 4 years without a problem, one of the table that we replicate has been growing in columns, now it has 55 columns.

I have noticed a problem, when I update the last column on the table and waits for the change to be updated on the subscriber the change is not there. But if I replicate the first 40 columns it works.

Changes made:

1) Upgraded to SP4
2) Added some extra fields using sp_addreplcolumn

Is this a known bug? Any ideas?

Regards

It looks like the adding of the column is not regenerating the triggers correctly. Could you profile the repladdcolumn and see if the trigger generation has any issue there?

On a side note, there are known issues with SQL 2000 + column tracking + vertical partitioning + DDL.

Is this a production box? I would then recommend contacting CSS.

Also would this have happened on SQL 2000 SP3 too? If you can test that too, it would be great.

|||Forgot to add that 55 is definitely not the limit for number of columns. The limit I think is 246 for SQL 2005 and I think it should be the same for SQL 2000 too.