Re: Managed vs. Automatic Identity Values
From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 09/08/04
- Next message: Douglas Tarr: "Re: General network error. Check your network documentation"
- Previous message: JimMac: "Managed vs. Automatic Identity Values"
- In reply to: JimMac: "Managed vs. Automatic Identity Values"
- Next in thread: JimMac: "Re: Managed vs. Automatic Identity Values"
- Reply: JimMac: "Re: Managed vs. Automatic Identity Values"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 8 Sep 2004 11:05:37 -0400
yes. Not For Replication is needed whenever you have any form of
bi-directional replication (except immediate updating where you don't need
it on the publisher).
It doesn't matter if you use automatic or manual strategies for identity
range management.
-- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html "JimMac" <JimMac@discussions.microsoft.com> wrote in message news:D6B87EA5-57EC-438E-8FC3-59E8A9645CA0@microsoft.com... > Does anyone know: if you go the Automatic ID Range handling method and let > SQL Server do this via SP_Addmergearticle values of @auto, @thresh, etc. > > Are you STILL required to set the NOT FOR REPLICATION property on your tables? > or is that not needed? Is NOT FOR REPL ONLY if you go the manual method? > > Thanks much in advance > Jim > Boston USA
- Next message: Douglas Tarr: "Re: General network error. Check your network documentation"
- Previous message: JimMac: "Managed vs. Automatic Identity Values"
- In reply to: JimMac: "Managed vs. Automatic Identity Values"
- Next in thread: JimMac: "Re: Managed vs. Automatic Identity Values"
- Reply: JimMac: "Re: Managed vs. Automatic Identity Values"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|