<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 High Availability
»
Peer-to-peer replication and identity columns...
Peer-to-peer replication and identity columns
Rate Topic
Display Mode
Topic Options
Author
Message
jchamiak
jchamiak
Posted Monday, January 21, 2013 8:12 AM
SSC Rookie
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:20 AM
Points: 31,
Visits: 661
All of the articles regarding identity columns for peer-to-peer replication talk about setting identity ranges when writing to multiple members at the same time. In my case, It's going to be configured as a DR solution so only the primary site will receive updates unless there is a need to fail over to the secondary site which will be rare. Only one member will ever be making updates at any given time. In my implementation I would think that it would be desirable to have no identity ranges configured and to have replicated commands update the identity values so that the primary and secondary sites are in sync. Does this sound like a reasonable configuration?
Post #1409574
Bhuvnesh
Bhuvnesh
Posted Tuesday, January 22, 2013 5:02 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562,
Visits: 3,451
jchamiak (1/21/2013)
In my implementation I would think that it would be desirable to have no identity ranges configured and to have replicated commands update the identity values so that the primary and secondary sites are in sync.
In transactional replication every article (table ) should have PK (in this case identity column as PK), So in P2p replication both side's table will have same schema (same identity column..same PK). so i dont think you can implement that , but better TEST what you think.
-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post
Post #1409954
EdVassie
EdVassie
Posted Monday, January 28, 2013 6:18 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 8:57 AM
Points: 2,619,
Visits: 2,749
What you want to do sounds similar to what we have done.
We use P2P but send all our updates to a single node, which is identified using a DNS vanity name. At failover time we update the vanity name and our apps then connect to the new master node.
There one problem we have had to overcome. P2P does not update the identity seed value on receiving nodes. This means that after failover the new master node will want to insert records using an identity value that is already in use.
We have overcome this by writing some code that keeps track of identity value high-water mark, and automatically applying appropriate CHECKIDENT RESEED commands to the new master node at failover.
Author:
SQL Server FineBuild
1-click install and best practice configuration of SQL Server 2012, 2008 R2, 2008 and 2005.
25 March 2013
: now over 23,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1412391
jchamiak
jchamiak
Posted Friday, February 01, 2013 9:10 AM
SSC Rookie
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 7:20 AM
Points: 31,
Visits: 661
EdVassie (1/28/2013)
What you want to do sounds similar to what we have done.
We use P2P but send all our updates to a single node, which is identified using a DNS vanity name. At failover time we update the vanity name and our apps then connect to the new master node.
There one problem we have had to overcome. P2P does not update the identity seed value on receiving nodes. This means that after failover the new master node will want to insert records using an identity value that is already in use.
We have overcome this by writing some code that keeps track of identity value high-water mark, and automatically applying appropriate CHECKIDENT RESEED commands to the new master node at failover.
This is something that I will likely need to do as well. Now at least I have an idea to start with. Thanks for the feeback.
Post #1414728
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
