Article View: borland.public.interbase.replication
Article #81Re: Books or Articles on Replication Strategy
From: Robert Schieck TeamB
Date: Sat, 24 Dec 2005 12:00
Date: Sat, 24 Dec 2005 12:00
23 lines
1572 bytes
1572 bytes
Rick Long wrote: > We are starting our first replication project and would like to learn > best practices before we experience "what not to do". Example: How > to allow users in two locations to add new Orders where the Order > number needs to be unique? One way is to have a unique identifer stored in eache server that is used in the primary key to make sure what comes out is unique.... If you only have a few machines, 'a' ,'b', 'c' works.... Another less secure way is to partition the "numers" amongst the machines. Server 1 starts uses 0 to 100 for keys, server 2 uses 200 to 300 etc. Of course you can expand the ranges but there is a chance of overlap if one server creates too many records and goes byond its range. hth -- Rob Schieck TeamB
Technical Details
Message-ID:
<43ad4654$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<43ac65f6$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: f89d7,8c6f4eaab4412593 X-Google-Attributes: gidf89d7,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Robert Schieck (TeamB)" <> Subject: Re: Books or Articles on Replication Strategy Newsgroups: borland.public.interbase.replication References: <43ac65f6$1@newsgroups.borland.com> Organization: MER Systems Inc. User-Agent: XanaNews/1.17.6.5 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 NNTP-Posting-Host: 69.17.157.16 Message-ID: <43ad4654$1@newsgroups.borland.com> Date: 24 Dec 2005 05:00:04 -0700 X-Trace: newsgroups.borland.com 1135429204 69.17.157.16 (24 Dec 2005 05:00:04 -0700) Lines: 23 Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news2.volia.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail