High keys and replication

  • I've just started in a new job and have been handed a handover document which states that the replication of a SQL 2000 database failed because the database schema uses 'high keys'.

    I have been unable to find any explanation on the web or in my SQL text books as to what a 'high key' might be.

    Could anyone enlighten me ?

    thanks for your help

    Ian Harris

  • What replication mode you are using - transactional or merge? Merge replication have to resole key value confict.

    Good Luck !!

  • I think they are refering to the numericaly high value of the primary key in the table.  With Merge replication, if you are using numerical, seeded identity columns SQL server assigns a range of ID's to both the publisher and subscribers.  This range will have a threshold of 80% by default.  This means that when you get past 80% threshold the high value of the indexes can become a problem especialy when you are inserting large amounts of data (ie an import from a file) at a time and the threshold value is exceeded.  Check the properties of the article in question to change these values and perhaps try using a bigger range or scripting the refresh / renewal of an index range.

    Cheers

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

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