| Author |
Topic |
|
dolphin123
Yak Posting Veteran
84 Posts |
 Posted - 2014-05-12 : 16:28:44
|
Hi,I set up transaction replication for certain tables. I am getting the error:Cannot insert explicit value for identity column in table '<tablename>' when IDENTITY_INSERT is set to OFF. I see the cause of the issue. Publisher table is trying to dump the data to the Subscriber table where it's identity column is not allowing any data.One way to workaround this issue is making the subscriber database's identity column not IDENTITY. but we have to keep both table's schema identical. Is there a configuration in the replication that I missed causing this issue? Surely Someone in the past would have wanted to keep the same value on both tables.Any help is appreciated.D |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-05-12 : 16:33:37
|
| http://dba.stackexchange.com/questions/21831/sql-server-2008-r2-transactional-replication-cannot-insert-explicit-value-for-iTara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
dolphin123
Yak Posting Veteran
84 Posts |
Posted - 2014-05-13 : 16:33:14
|
| Thanks so much.Now, I am trying to change the subscriber tables' primary keys' "no for replication" property to Yes. If I try to do it using UI (Design table option), it says it cannot be done. I have to recreate the table. If I use the command:EXEC sys.sp_identitycolumnforreplication <tableobjectid>, 1It says "Command ran successfully" but it doesn't change the option. Is there a step I am missing?Again, appreciate your help |
|
|
|
dolphin123
Yak Posting Veteran
84 Posts |
Posted - 2014-05-13 : 16:35:14
|
| Could it be because I am changing this on subscriber and the publisher's property is changing it back to NO? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2014-05-13 : 18:25:28
|
| You need to run it on the publisher.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
dolphin123
Yak Posting Veteran
84 Posts |
Posted - 2014-05-14 : 01:07:49
|
| It is quite odd. If I close the SQL management studio and reopen it again after running the SP command, it works fine. Tara - I am curious. Why should I make this change on publisher? It is the subscriber that needs this ability (No for replication) right?My understanding is that "no for replications" will do the following:- it sees a direct insert, it creates an ID that is an incremental from the previous ID. - it sees an replication insert, it would take the value comes in and update the rows.If I am right, why would I run this on publisher? it should only be on subscriber. why am I wrong here? Thank you !! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
dolphin123
Yak Posting Veteran
84 Posts |
Posted - 2014-05-14 : 13:58:49
|
| Thanks a lot AGAIN!! |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
Transaction Replication - Identity Insert
Tara Kizer