Re: id manage problem with ID RANGES in merge.

Tech-Archive recommends: Speed Up your PC by fixing your registry



Check to see that the constraints are what they should be. Automatic
Identity Range Management has two parts, the identity seed and the identity
constraint. Both pieces have to be correct for it work.

--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

"Tejas Parikh" <TejasParikh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:616D6CE9-BF00-43D1-99B4-42E6A6E17EB9@xxxxxxxxxxxxxxxx
> Hey. I've set auto id ranges in my publication.
> when i do dbcc checkident(tablename) on pub and sub, it shows me different
> id ranges. i ran a sp_adjustpublisheridentityrange pubname and it said
> 'the
> command completed successfully'. I can do updates and deletes at the sub
> and
> it gets replicated to the pub. When i try to add a row to sub, it says
> that
>
> 'Server: Msg 548, Level 16, State 2, Line 1
> The identity range managed by replication is full and must be updated by a
> replication agent. The INSERT conflict occurred in database 'eSmart',
> table
> 'defLanguages', column 'LanguageID'. Sp_adjustpublisheridentityrange can
> be
> called to get a new identity range.
> The statement has been terminated.'
>
> I've checked a lot of things but they say i did it correctly but it keeps
> giving me this error. I even restarted the agent on my test box but the
> merge
> agent doesn't take care of the ranges. FYI, I'm nowhere close to filling
> up
> my ranges. and the threshold is 80% on a 700000 id range for each(pub and
> sub).
>
> please help


.



Relevant Pages

  • Re: merge replication - enabling identity range management
    ... replication agent. ... to get a new identity range. ... > 2 subscribers) and enabled identity range management. ... > publisher and the other subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: a different identiy columns in replication question
    ... Looking for a book on SQL Server replication? ... >> With immediate updating you are guananteed not to have identity range ... >> applied on the publisher where the publisher's identity range rules. ... updates can still occur on the publisher. ...
    (microsoft.public.sqlserver.replication)
  • RE: Merge Replication Issues
    ... constraints on one table for inserts and both are from replication. ... using automatic identity range management. ... > Then the website started to hit problems. ...
    (microsoft.public.sqlserver.replication)
  • Merge Replication Issues
    ... Basicall I have a SQL 2000 Server, that is the publisher for a merge ... This merge replication, is to replicate to handhelds, that via ... The publisher is not however. ... using automatic identity range management. ...
    (microsoft.public.sqlserver.replication)
  • Re: Identity Range Merge Replication Problem
    ... replication agent. ... The INSERT conflict occurred in database 'Car', ... get a new identity range. ...
    (microsoft.public.sqlserver.replication)