[dba-SQLServer]Issues with Multiple Subscriptions

Thanks David.
I believe the process only takes about 10 minutes to replicate.
However, if I have data synchronizing between ServerA and ServerB,
what's gonna happen when ServerA tries to sync with ServerC?  Will I
receive an error?  Will data not be fully replicated?

Mark


-----Original Message-----
From: David McAfee [mailto:DMcAfee at haascnc.com] 
Sent: Thursday, October 30, 2003 4:31 PM
To: 'dba-sqlserver at databaseadvisors.com'
Subject: RE: [dba-SQLServer]Issues with Multiple Subscriptions

One thing to check is how long the replication lasts. We had a developer
set a db to replicate every 10 minutes...the problem was that the
replication itself took longer than 10 minutes. The processor was
crawling.

D

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of Mark
Boyd
Sent: Thursday, October 30, 2003 12:51 PM
To: SQLServerList
Subject: [dba-SQLServer]Issues with Multiple Subscriptions


I am in the process of creating 3 Push Subscriptions from 1
Distributor/Publisher.

Basically, I need all 4 SQL Servers to have the same data replicated
between each other.

 

Are there any known issues with setting up all 3 Replication Schedules
to run at the same times during the day?  I want to have the data
replicated every 15 minutes, between 5:00AM and 11:00PM.  Is there a
problem with each push having the same start time, or should I have each
start about 5 minutes after each other?

 

Are there any other issues I should consider?

 

TIA,

Mark Boyd

Sr. Systems Analyst

McBee Associates, Inc.

 

_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com