Replication (non merge) - identity columns

  • We have a dev SQL server that is setup to subscribe to the live server for replication (excuse my terminology, I'm not familiar with replication).

    The problem I am having is entering test data into the dev database - I get a pk constraint error on a table with an auto-incrementing pk even though I am not trying to insert an id directly:

    Violation of PRIMARY KEY constraint 'PK_siteSection'. Cannot insert duplicate key in object 'dbo.SiteSection'.

    I am wondering if:

    a) this behaviour expected (ie. it's because of replication)

    b) the dev server should be setup as a subscriber to live

    c) if yes and yes; what can be done to allow inserts into the dev db

    I hope that makes sense and thanks for your time,

    Dominic

  • Turns out this is intended and this dev db is called a 'live dev'. We then have a 'dev dev' for playing with (I've only been here a day... no one but the manager was aware of this...).

    Apologies for the wasted post.

    Closed.

    Dominic

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply