December 21, 2010 at 2:48 am
Hi Experts,
We are facing a Replication Truncation problem on production
Actually in july we have removed one table from replication & then we altered one column (we made varchar 500, before it was varchar 255) and then again we added the table into replication & it was working fine.
Recently in Nov. someone needed to restart the replication & after that we are facing truncation error for that column, We observed that the stored procedure sp_MSins_cc_appHistory is revert back to the old defination for that column as varchar (255)!
My question is why it is change to varchar 255 & how it can be change to varchar(500)? can we modify these stored procedures?
or is there any other solution for this?
Thanks for your help!
December 21, 2010 at 6:45 am
http://technet.microsoft.com/en-us/library/ms187946.aspx - This procedure, sp_scriptpublicationcustomprocs, will create the procedures for you. A couple of notes here, first set your text output in SSMS to largest possible, second this is run on the publisher database. The scripts that are generated are run on the subscription database.
Use carefully and read the directions. 🙂
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
December 22, 2010 at 5:27 am
Thanks for reply,
can we modify directly these stored procedure sp_MSins, sp_MSupd & sp_MSdel to make small change like we need to make one parameter of sp_MSins from varchar(255) to varchar(500)!
Thanks,
December 22, 2010 at 7:11 am
You can BUT I would strongly recommend that you use the procedure I pointed out to build them. That will build them to match the publisher (and hopefully the subscriber).
😉
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply