July 15, 2008 at 12:41 pm
We are using merge replication for a very large table, BigLog, and as part of an application change we added 3 columns to the table BigLog on one of the participating servers. We see the additional columns when looking at the publication / article on this server and they are not selected as I would suspect.
What I am wondering is, can we just add the columns on the BigLog table on the other participating servers and once complete select the columns in the article properties within the publication to get that aspect of the merge replication going or do we have to rebuild the merge publication in order for this to be seen appropriately for all servers.
I will be testing this as well to see what the best approach would be, I just want to get some further input / feedback from experience before we do this as the table is really big and I don't want to mess this up.
Thanks in advance for any information you can provide.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
July 15, 2008 at 1:02 pm
Well, testing revealed that you can't do this. I was unable to add columns to the subscriber table. Sorry, new to merge replication.... : )
I guess it is a re-push of the data.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
July 21, 2008 at 8:41 am
in SQL 2000, you can use exec sp_repladdcolumn to add a column into a replicated table, system will propagate the change to suscriber automatically
in SQL 2005, you can use "alter table T add column ..." to add column straightforward, SQL server will take care of the rest processing automatically.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply