Post reply

The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @identityrangemanagementoption property is auto Using SQL Server2005 Merge Replication

  • July 12, 2008 at 12:18 am

    #193886

    Hi,

    I am trying to configure Replication for a production DB which is using SQL Server 2005, after creating a merge replication pulisher and pushing the subscriber, if i try to start the snapshot, i am getting the following error, so please suggest.

    The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure that the value for the @identityrangemanagementoption property is auto.

    With Regards

  • July 12, 2008 at 2:32 am

    #841956

    When you use merge replication on tables with an identity column you have to set ranges for each replication partner to avoid Identity insert conflicts. So if you have to replication partners define a range of 0 - 100000 on the first server and 100001 - 200000 on the second. This way you avoid that the same identity value is created on both sides.

    I don't have a replication setup right now, so I can't tell you in which screen exactly you can define these settings, but If I remember right it's in the article properties. You have to set a range for each table containg an Identity column.

    [font="Verdana"]Markus Bohse[/font]

  • July 12, 2008 at 2:45 am

    #841959

    Ok fine, thanks a lot. Now the DBs which are used for replication, i have already pushed the dbs , so should i delete them, and reseed for all the tables in both publisher db and subscriber db and then set up the replication after changing the seed value.

    I hope i can use in the same for all the tables available in both the DB which has been used for replicatoin by changing the range values.

    DBCC CHECKIDENT (tblname, RESEED, 740000000)

    thanks a lot

    with Regards

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

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