Identity messed up on merge replication

  • You're welcome.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Dominic Gagné (11/23/2010)


    thanks for the hints. I was figuring something like that to "rescue" the data on subscribers. that'll be a pain, but, no pain no gain! 🙂

    thanks all for your precious help

    Your welcome. Just remember your cascading dependencies!


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • When you add a table with an IDENTITY column to a publication in merge replication, there is an option (both in the system sproc and the GUI) to make the replication agent assign different identity ranges to each subscriber. Have you set this option?

Viewing 3 posts - 16 through 17 (of 17 total)

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