Re: id manage problem with ID RANGES in merge.
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sun, 20 Nov 2005 18:15:34 -0500
Have you reviewed this http://www.simple-talk.com/2005/07/05/replication/
yet? There is also BOL which is perhaps a little vague.
I am a little confused by your post. You state "Even at that point, the
ranges were
> 700000 for both pub and sub. And as far as my understanding goes, the
> range
> at pub should have been from 1-700000 and 700001-1400000. "
Are you saying the range at the pub for the same article was 1-700000 and
700001-1400000? Or do you mean the range at the pub was 1-700000 and the
range at the sub was 700001-1400000. The latter is correct.
There is a bug when you drop the subscription the replication check
constraint remains. This isn't a problem unless you do a no-sync
subscription or if you have one of the name conflict sections which does not
clobber the table when the snapshot is applied. There options are the Keep
the existing table unchanged, delete all data, and delete all data which
matches the row filter statement.
You might not be able to delete the check constraints but you should be able
to alter them
--
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:7B81F1D9-EB1B-479F-9E05-AB76A1BC4309@xxxxxxxxxxxxxxxx
> See, one thing I dont understand with this is that
> I had gotten it to work at one point. Even at that point, the ranges were
> 700000 for both pub and sub. And as far as my understanding goes, the
> range
> at pub should have been from 1-700000 and 700001-1400000. But it was not
> like
> that even though the whole process worked. The ranges were different but
> not
> the ones mentioned above for some reason.
>
> I had tried this process a few times. If it didn't work I would delete the
> subscription and then the publication. And then start again. Is this the
> reason why it messed up the id ranges? And also, SQL should not let me
> delete
> the check constraints as they r being used by replication, right? but in
> my
> case, it does. and then when i try to recreate them, it gives me the error
> 548 copied in the previous thread. I'm getting really confused now...
>
> Thank you for all your help.
.
- References:
- Re: id manage problem with ID RANGES in merge.
- From: Hilary Cotter
- Re: id manage problem with ID RANGES in merge.
- Prev by Date: Re: id manage problem with ID RANGES in merge.
- Next by Date: Re: merge replication - portability of subscriber
- Previous by thread: Re: id manage problem with ID RANGES in merge.
- Index(es):
Relevant Pages
|
