Two distant locations 
Author Message
 Two distant locations
Hi all:

I need to have 2 locations connected by a T1 running the exact same
database. How do I avoid people making entries at the databases at the same
time and having duplicate entries.

Client would like to use the servers like a cluster but instead of the one
database just sitting idle, people in the area would make thier entries on
this database. While people close to the other database would make thier
entries at that one. If one goes down the other would fullfill all entries.

Any ideas?

Eric Freitag



Thu, 22 Apr 2004 13:07:55 GMT
 Two distant locations

Eric,

It sounds as if merge replication is what you're looking for.  Server A acts as a publisher, with Server B acting as subscriber.  Each are completely
autonomous entities:  users at Site A can use server A and users at Site B can use Server B.  When the merge agent runs, it reconciles net changes from
Server B to Server A, then does the same thing in reverse.  

I would direct you to Books Online topic "How Merge Replication Works" for more information here.

HTH!
Ryan Stonecipher
Microsoft Product Support
SQL Server Data Services

Hello, I'm the humble disclaimer. Nobody really likes me. I'm used to being ignored and maligned - I still get the job done.  If you cared enough to read
me, then you'd learn that this posting is provided "AS IS" with no warranties, and confers no rights.  You assume all risk for your use.  (C)2001 Microsoft
Corporation.  All rights reserved.



Thu, 22 Apr 2004 18:35:37 GMT
 Two distant locations
Thanks Ryan I will look into that. One question if they are both separate
servers with the same database how does the database keep an incremented
number (primary key) from having the same number.

For example we are at number 30 on both servers how do you prevent both
servers using #30 inbetween merge replication?

Eric



Quote:
> Eric,

> It sounds as if merge replication is what you're looking for.  Server A

acts as a publisher, with Server B acting as subscriber.  Each are
completely
Quote:
> autonomous entities:  users at Site A can use server A and users at Site B

can use Server B.  When the merge agent runs, it reconciles net changes from
Quote:
> Server B to Server A, then does the same thing in reverse.

> I would direct you to Books Online topic "How Merge Replication Works" for

more information here.
Quote:

> HTH!
> Ryan Stonecipher
> Microsoft Product Support
> SQL Server Data Services

> Hello, I'm the humble disclaimer. Nobody really likes me. I'm used to

being ignored and maligned - I still get the job done.  If you cared enough
to read
Quote:
> me, then you'd learn that this posting is provided "AS IS" with no

warranties, and confers no rights.  You assume all risk for your use.
(C)2001 Microsoft
Quote:
> Corporation.  All rights reserved.



Fri, 23 Apr 2004 01:19:58 GMT
 Two distant locations
Hi Eric,

If you are using SQL Server 2000, then you can use the "Automated Identity
Range Handling" features introduced there.  Otherwise, check SQL Server
Books Online for the "NOT FOR REPLICATION" option for columns with the
IDENTITY property.

HTH!
--R


Quote:
> Thanks Ryan I will look into that. One question if they are both separate
> servers with the same database how does the database keep an incremented
> number (primary key) from having the same number.

> For example we are at number 30 on both servers how do you prevent both
> servers using #30 inbetween merge replication?

> Eric



> > Eric,

> > It sounds as if merge replication is what you're looking for.  Server A
> acts as a publisher, with Server B acting as subscriber.  Each are
> completely
> > autonomous entities:  users at Site A can use server A and users at Site
B
> can use Server B.  When the merge agent runs, it reconciles net changes
from
> > Server B to Server A, then does the same thing in reverse.

> > I would direct you to Books Online topic "How Merge Replication Works"
for
> more information here.

> > HTH!
> > Ryan Stonecipher
> > Microsoft Product Support
> > SQL Server Data Services

> > Hello, I'm the humble disclaimer. Nobody really likes me. I'm used to
> being ignored and maligned - I still get the job done.  If you cared
enough
> to read
> > me, then you'd learn that this posting is provided "AS IS" with no
> warranties, and confers no rights.  You assume all risk for your use.
> (C)2001 Microsoft
> > Corporation.  All rights reserved.



Fri, 23 Apr 2004 10:18:48 GMT
 Two distant locations
Thanks again Ryan I will check these out.

Eric


Quote:
> Hi Eric,

> If you are using SQL Server 2000, then you can use the "Automated Identity
> Range Handling" features introduced there.  Otherwise, check SQL Server
> Books Online for the "NOT FOR REPLICATION" option for columns with the
> IDENTITY property.

> HTH!
> --R



> > Thanks Ryan I will look into that. One question if they are both
separate
> > servers with the same database how does the database keep an incremented
> > number (primary key) from having the same number.

> > For example we are at number 30 on both servers how do you prevent both
> > servers using #30 inbetween merge replication?

> > Eric


message

> > > Eric,

> > > It sounds as if merge replication is what you're looking for.  Server
A
> > acts as a publisher, with Server B acting as subscriber.  Each are
> > completely
> > > autonomous entities:  users at Site A can use server A and users at
Site
> B
> > can use Server B.  When the merge agent runs, it reconciles net changes
> from
> > > Server B to Server A, then does the same thing in reverse.

> > > I would direct you to Books Online topic "How Merge Replication Works"
> for
> > more information here.

> > > HTH!
> > > Ryan Stonecipher
> > > Microsoft Product Support
> > > SQL Server Data Services

> > > Hello, I'm the humble disclaimer. Nobody really likes me. I'm used to
> > being ignored and maligned - I still get the job done.  If you cared
> enough
> > to read
> > > me, then you'd learn that this posting is provided "AS IS" with no
> > warranties, and confers no rights.  You assume all risk for your use.
> > (C)2001 Microsoft
> > > Corporation.  All rights reserved.



Fri, 23 Apr 2004 11:32:50 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. two locations

2. Sync data between 2 SQL servers in two locations at intervals

3. backups written to two different locations

4. Two Database (one in fix location and one in PC portable)

5. writing logs to two different locations on the same server

6. Retrieve data from two tables, from two databases, in two registered servers

7. Open Two Database with Two System.Mda and Two different User Names and Password

8. cross platform distant access to sql server

9. Distant clusters

10. Probleme accès approuvé depuis un domaine distant

11. Send updates to distant web server

12. sp_oacreate and distant DLL


 
Powered by phpBB® Forum Software