Tim,
Glad to hear that you have resolved the identity issue. Sorry that it was
such a trouble.
John Gose
MCDBA
Microsoft SQL Server Support
This posting is provided "AS IS", with no warranties, and confers no rights
Are you secure? For information about the Microsoft Strategic Technology
Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
--------------------
| Subject: Re: merge replication identity conflict madness!!
| Date: Tue, 18 Feb 2003 10:00:25 -0000
| Lines: 115
|
<Snip of Header Stuff>
|
| grrrr
| found it
|
| to make replication work, you have to set the option "not for replication"
| on identity fields. What a totally unobvious thing to have to do!!!
|
| how come setting up Access to synchronise is so easy, and data changes are
| replicated, and id columns are handled properly, yet sql server makes
| replication look like an after thought.
|
|
| Tim
|
|
|
| > not quite there yet....
| >
| > the option to turn on automatic identity handling is grayed out, and
| > whatever I do I cannot make it available. I have deleted all
subscribers,
| > and recreated the publication with no joy.
| >
| > am I missing something obvious again?
| >
| >
| > thanks
| >
| > Tim
| >
| >
| > > thanks John,
| > > my faith is sql server is restored!!!!
| > >
| > >
| > > Tim
| > >
| > >
| > > > Tim,
| > > >
| > > > Take a look at BOL Replication->Managing Identity Values. What you
| > > > probably wanted to do was have SQL handle the ranges automatically.
| > This
| > > > is a property of the article (the little grey button to the right of
| the
| > > > table name) that allows you to set ranges for each computer to use.
| > > > Unfortunately, it needs to be setup prior to any subscriptions being
| > > > created.
| > > >
| > > > John Gose
| > > > MCDBA
| > > > Microsoft SQL Server Support
| > > >
| > > > This posting is provided "AS IS", with no warranties, and confers no
| > > rights
| > > >
| > > > Are you secure? For information about the Microsoft Strategic
| Technology
| > > > Protection Program and to order your FREE Security Tool Kit, please
| > visit
| > > > http://www.microsoft.com/security.
| > > >
| > > >
| > > > --------------------
| > > > | Subject: merge replication identity conflict madness!!
| > > > | Date: Mon, 17 Feb 2003 16:11:02 -0000
| > > > | Lines: 25
| > > > |
| > > > <Snip of Header Stuff>
| > > > |
| > > > | Hi all,
| > > > |
| > > > | I have a database with integer identity columns as primary keys,
| > > starting
| > > > at
| > > > | 1 and incrementing by 1.
| > > > |
| > > > | When I set up merge replication (from sql 2000 to sql 2000) on 2
| other
| > > > | laptops, we get conflicts every time we synchronize. And this
| > conflict
| > > is
| > > > | on the PK identity column.
| > > > |
| > > > | Having read the archives someone said I have to manually change
the
| > seed
| > > > | value of every primary key in the database, for every laptop that
is
| > > > | planning to synchronize. (100 tables, 20 laptop users = too much
| > > work!!!)
| > > > |
| > > > | Please tell me this isn't the case!!
| > > > |
| > > > | Please please point me in the right direction
| > > > |
| > > > |
| > > > |
| > > > | ta
| > > > |
| > > > |
| > > > | Tim
| > > > |
| > > > |
| > > > |
| > > >
| > >
| > >
| >
| >
|
|
|
by