Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a one way transactional replication set up between two 2005 MS Sql servers. Recently I have started to receive the following message in the replication monitor from the subscriber:

Table 'dbo.tblname' does not have the identity property. Cannot perform SET operation. (Source: MSSQLServer, Error number: 8106)

Will adding the identity column to 'dbo.tblname' on the subscriber resolve this error or do I need to drop and re-add the subscription?

share|improve this question

migrated from Mar 15 '12 at 12:46

This question came from our site for professional and enthusiast programmers.

There is no need to add an identity column for no reason.

My guess is someone is issuing a SET IDENTITY_INSERT ON when there is no identity column in this table.

You need to check the code to make sure it is correct.

share|improve this answer
up vote 0 down vote accepted

Re-adding the subscription did not resolve this issue. The scheme created replication snapshot agent added a SET IDENTITY_INSERT 'dbo.tblname' ON for record inserts to the insert and update stored procedure.

A manual edit to remove the SET IDENTITY_INSERT 'dbo.tblname' ON from the stored procedures was all that was required.

However this will be an issue when I run the snapshot agent in the future.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.