I understand the "Not for replication" clause for Identity columns. What I
don't understand is how to give each subscriber a different range of IDs.
Can someone please explain?
Thanks,
Paul.
by Paul Wrag » Mon, 11 Dec 2000 11:49:50
Thanks,
Paul.
by Ivan Arjentinsk » Mon, 11 Dec 2000 19:13:29
In SQL 7 - use IDENTITY start parameter.
In SQL2000 - use Auto Identity Range handling - see BOL.
HTH
Ivan Arjentinski
-----------------------------------------------
Please answer only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
can be cut and pasted into Query Analyzer is appreciated.
-----------------------------------------------
Quote:> I understand the "Not for replication" clause for Identity columns. What I
> don't understand is how to give each subscriber a different range of IDs.
> Can someone please explain?
> Thanks,
> Paul.
by Paul Wrag » Tue, 12 Dec 2000 02:49:16
(Using 7.0). I don't understand what you mean by "Use IDENTITY start
parameter". What command is this a parameter to?
Paul.
> In SQL 7 - use IDENTITY start parameter.
> In SQL2000 - use Auto Identity Range handling - see BOL.
> HTH
> Ivan Arjentinski
> -----------------------------------------------
> Please answer only to the newsgroups.
> When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which
> can be cut and pasted into Query Analyzer is appreciated.
> -----------------------------------------------
> > I understand the "Not for replication" clause for Identity columns. What
I
> > don't understand is how to give each subscriber a different range of
IDs.
> > Can someone please explain?
> > Thanks,
> > Paul.
by Graeme Slogrov » Thu, 01 Mar 2001 15:40:54
dbcc checkident(table_name, RESEED, xxxxxxxxxxx)
Where xxxxx is the starting value you want on the remote side for the
identity column.
Quote:> I understand the "Not for replication" clause for Identity columns. What I
> don't understand is how to give each subscriber a different range of IDs.
> Can someone please explain?
> Thanks,
> Paul.
1. merge replication and identity partition
Check out the following page in Books Online for complete information:
Use the NOT FOR REPLICATION Option on the IDENTITY Property
--
KNV
Check out http://members.tripod.com/~vyaskn/SQLServerRes.html for SQL Server
resources on the net.
Always under construction!!!
I have this problem:
I need to have two site in merge replication but i want identity partition
(1 site identity 1 to 1000, 2 site 1001 to 2000).
how can i DO?
how can i put NOT FOR REPLICATION from GUI ?
thanks
2. Question about Mouse Event.
3. problem with merge replication and identity column
5. Use of guid and identity columns in merge replication
6. Oracle Financials Consultants - Available
7. Conflict with Identity column in merge replication
8. Dbase,Access,Foxpro pros and cons
9. Identity columns and merge replication
10. Merge Replication occasionally reseeds my @#$@#$# IDENTITY columns! 8(
11. Handling IDENTITY column in Merge Replication
12. Merge replication with identity value ranges using not for replication option
13. Changing Identity column to Identity not for replication?