Identity error in replication

I have replication set up from server A to server B. One of the tables used
in publication has an identity column but is set up for (NOT FOR
REPLICATION) . I also have the same setup on subscriber too. Am I getting
this error due to that.
{CALL sp_MSupd_table
(NULL,NULL,NULL,NULL,'N',NULL,NULL,NULL,NULL,NULL, NULL,NULL,NULL,NULL,NULL,2005-
02-25 00:00:00.000,57502,0x1080)}
Should I have NFR turned off on the identity column in subscriber? If so
will it create any duplicate ids at subscriber end? Any solution will be
greatly appreciated.
TIA
Message posted via http://www.sqlmonster.com
From the name of the sp, it appears you are using transactional replication.
Is this TR with updating subscribers or non-updating. Normally in either
case there shouldn't be an identity column on the subscriber. If the
subscriber is updating with a queue set up, then thye identity column is
needed and you'll need to ensure the identity ranges don't overlap - either
using automatic or manual range management.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||You are right we do have transactional replication set up. In this case we
do have the subscriber as updatable which is why we need the identity
turned on for the id columns. If so why is that we are getting this error
and how do we fix this?
Message posted via http://www.sqlmonster.com
|||If the subscriber is updatable, you do not need the identity attribute, and
it shouldn't be there. The publisher allocates the identity value using 2PC
distributed transactions. The subscriber just has a normal int column.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)