| Groups | Blog | Home |
sql server replication : Replication on identity column
replication on this table and sync the subscriber, it created the column with int datatype Table A on subscriber. I want the Subscriber to retain the identity column so that in case of Publisher failure application can use subscriber. How to achive this.
Use queued updating subscribers. This'll also take care of the identity seed
being useable on the subscriber. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
What you have to do is
1) create the schema on the other side with the NFR attribute for the identity property. 2) put the data in place 3) on the publisher have a seed of 1, and an increment of 2. 4) on the subscriber have a seed of 2 and an increment of 2. 5) issue a dbcc checkident(tablename) on the publisher to get the latest assigned value. If its even, make it the next higher odd value. 6) issue a dbcc checkident(tablename) on the subscriber to get the latest assigned value. If its odd, make it the next higher even value. 7) do a no sync subscription. Using queued replication will introduce triggers and a guid column which may or may not work for you. Queued is also designed for situations where the majority of the DML originates on the publisher, and it is not scalable beyond 10 subscribers. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 [quoted text, click to view] "Satwinder" <Satwinder@discussions.microsoft.com> wrote in message news:BD42C0FB-54E7-47C4-973B-8819D64D7CA9@microsoft.com... >I have a column in table A with identity value. When i enable Transaction > replication on this table and sync the subscriber, it created the column > with > int datatype Table A on subscriber. > > I want the Subscriber to retain the identity column so that in case of > Publisher failure application can use subscriber. > > How to achive this. > > Satwinder
Can i alter the custom Stored procs (sp_MSins_/sp_MSupd_,sp_MSdel) and achive
this. Satwinder [quoted text, click to view] "Hilary Cotter" wrote:
> What you have to do is > > 1) create the schema on the other side with the NFR attribute for the > identity property. > 2) put the data in place > 3) on the publisher have a seed of 1, and an increment of 2. > 4) on the subscriber have a seed of 2 and an increment of 2. > 5) issue a dbcc checkident(tablename) on the publisher to get the latest > assigned value. If its even, make it the next higher odd value. > 6) issue a dbcc checkident(tablename) on the subscriber to get the latest > assigned value. If its odd, make it the next higher even value. > 7) do a no sync subscription. > > Using queued replication will introduce triggers and a guid column which may > or may not work for you. Queued is also designed for situations where the > majority of the DML originates on the publisher, and it is not scalable > beyond 10 subscribers. > > -- > Hilary Cotter > Director of Text Mining and Database Strategy > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. > > This posting is my own and doesn't necessarily represent RelevantNoise's > positions, strategies or opinions. > > 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 > > > > "Satwinder" <Satwinder@discussions.microsoft.com> wrote in message > news:BD42C0FB-54E7-47C4-973B-8819D64D7CA9@microsoft.com... > >I have a column in table A with identity value. When i enable Transaction > > replication on this table and sync the subscriber, it created the column > > with > > int datatype Table A on subscriber. > > > > I want the Subscriber to retain the identity column so that in case of > > Publisher failure application can use subscriber. > > > > How to achive this. > > > > Satwinder > >
Yes you can, but it offers very bad performance. Its simply not scalable.
-- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 [quoted text, click to view] "Satwinder" <Satwinder@discussions.microsoft.com> wrote in message news:C36A33CE-35E5-469F-99FE-F6F51782CAD8@microsoft.com... > Can i alter the custom Stored procs (sp_MSins_/sp_MSupd_,sp_MSdel) and > achive > this. > > Satwinder > "Hilary Cotter" wrote: > >> What you have to do is >> >> 1) create the schema on the other side with the NFR attribute for the >> identity property. >> 2) put the data in place >> 3) on the publisher have a seed of 1, and an increment of 2. >> 4) on the subscriber have a seed of 2 and an increment of 2. >> 5) issue a dbcc checkident(tablename) on the publisher to get the latest >> assigned value. If its even, make it the next higher odd value. >> 6) issue a dbcc checkident(tablename) on the subscriber to get the latest >> assigned value. If its odd, make it the next higher even value. >> 7) do a no sync subscription. >> >> Using queued replication will introduce triggers and a guid column which >> may >> or may not work for you. Queued is also designed for situations where the >> majority of the DML originates on the publisher, and it is not scalable >> beyond 10 subscribers. >> >> -- >> Hilary Cotter >> Director of Text Mining and Database Strategy >> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. >> >> This posting is my own and doesn't necessarily represent RelevantNoise's >> positions, strategies or opinions. >> >> 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 >> >> >> >> "Satwinder" <Satwinder@discussions.microsoft.com> wrote in message >> news:BD42C0FB-54E7-47C4-973B-8819D64D7CA9@microsoft.com... >> >I have a column in table A with identity value. When i enable >> >Transaction >> > replication on this table and sync the subscriber, it created the >> > column >> > with >> > int datatype Table A on subscriber. >> > >> > I want the Subscriber to retain the identity column so that in case of >> > Publisher failure application can use subscriber. >> > >> > How to achive this. >> > >> > Satwinder >> >> >>
You'll also have problems on failover, as the identity values will clash
(typically this'll cause PK problems). Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
While this will work, setting identity_insert off and on in a proc before
doing an update is very expensive and can only be done on a single table at a time. This will essentially cause any parallel operations to become serialized. I strongly do not recommend doing this as it simply is not a scalable solution. -- Hilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 [quoted text, click to view] "Satwinder" <Satwinder@discussions.microsoft.com> wrote in message news:97AD6E0E-75C3-4916-89F4-D6F41F613BD8@microsoft.com... > There is a very good article telling how to achive identity column > replication while maintaining the identity property at subscriber. > > http://www.databasejournal.com/features/mssql/article.php/3483421 > > have a look at it. > > cheers > Satwinder.. > > "Paul Ibison" wrote: > >> You'll also have problems on failover, as the identity values will clash >> (typically this'll cause PK problems). >> Cheers, >> Paul Ibison SQL Server MVP, www.replicationanswers.com >> >> >>
There is a very good article telling how to achive identity column
replication while maintaining the identity property at subscriber. http://www.databasejournal.com/features/mssql/article.php/3483421 have a look at it. cheers Satwinder.. [quoted text, click to view] "Paul Ibison" wrote:
> You'll also have problems on failover, as the identity values will clash > (typically this'll cause PK problems). > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com > >
Thanks for the link - in some senses though this is a manual way of
achieving the same thing that is automatic with queued updating subscribers but anyway I must admit that I hadn't thought of this as a potential solution before. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |