NFR with merge in em shows weird seed

I've set identity columns to automatic ranges with merge. The publisher
ranges is for a million and the subscriber side is for a million. Now, when I
go to the EM, and go to the Desgin Table in EM for a table, I see the
identity seed to 1. Is this normal? But when I ran the script and everything
and also when I go to the article properties, it shows the correct identity
ranges. Please let me know. thank you very much...
On the publisher this is correct. On the subscriber it should be at
1,000,001.
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@.discussions.microsoft.com> wrote in message
news:6B8E4284-B565-4D0C-90E5-5948AA21E136@.microsoft.com...
> I've set identity columns to automatic ranges with merge. The publisher
> ranges is for a million and the subscriber side is for a million. Now,
> when I
> go to the EM, and go to the Desgin Table in EM for a table, I see the
> identity seed to 1. Is this normal? But when I ran the script and
> everything
> and also when I go to the article properties, it shows the correct
> identity
> ranges. Please let me know. thank you very much...

NFR needed in Foreign Key constraint?

Chris,
have a look at this article:
http://support.microsoft.com/default.aspx?
scid=http://support.microsoft.com:80/support/kb/articles/q
302/3/41.ASP&NoWebContent=1
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
That's great for one row, but reality is multiple rows can get updated.
Will the NFR work, what are my options? Doing a backup/restore to synch
subscriber, do I drop all FK contraints after restore and replace w/ indexes?
What is best practice? Subscribers used to offload reporting, so selects only
occuring against subscr.
Thanks,
Chris
"Paul Ibison" wrote:

> Chris,
> have a look at this article:
> http://support.microsoft.com/default.aspx?
> scid=http://support.microsoft.com:80/support/kb/articles/q
> 302/3/41.ASP&NoWebContent=1
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||My understanding is that to have TR work for a multi-row
update, you'd need to disable the FKs entirely.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)