July 10, 2009 at 3:36 pm
Guys,
I am getting the following error in my transaction replication with pull subscription.
Command attempted:
if @@trancount > 0 rollback tran
(Transaction sequence number: 0x0002D83C00000847000100000000, Command ID: 1)
Error messages:
Invalid column name 'NUM'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
The column exists on both primary and secondary databases.
Below is the message from SQL Log
Date7/10/2009 4:32:46 PM
LogSQL Server (Current - 7/10/2009 4:32:00 PM)
Sourcespid52
Message
Replication-Replication Distribution Subsystem: agent xxxxxxxxVB01\SQL1-xxxxx-xxxxx_Publication-xxxxxxxVB02\SQL2-1 failed. Invalid column name 'NUM'.
I am not sure what is causing this error.
Any suggestions or inputs would help
Thanks
July 11, 2009 at 9:07 am
Was the column added after the setting up replication. I would stop replication and rebuild the subscription and replication again....
July 13, 2009 at 6:00 am
Try dropping the problem article and then readding it.
July 13, 2009 at 7:01 am
I think TRACEY is probably right here - the NUM column was added on the Publisher after replication was set up and that column already existed for the replicated table at the Subscriber. To prevent this happening in the future (assuming that you don't want the new column to be replicated) you can change the 'Replicate schema changes' option from True to False. You find that on the Subscription options page of the Publication Properties.
September 23, 2016 at 8:34 am
TRACEY-320982 (7/11/2009)
Was the column added after the setting up replication. I would stop replication and rebuild the subscription and replication again....
we did this and again the replication fails for a different table and a different column..
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply