Re: Database Replication
- From: "Adam Patrick Cassidy" <apcassidy@xxxxxxx>
- Date: Fri, 1 Dec 2006 11:27:53 -0500
Ryan,
I've been using transactional replication at my current employer for years
and latency will always be determined by geographic region and equipment.
In my case I'm seeing less than 5 second latency, usually lower than 2, and
yes, of course you can run queries on the data that is being replicated.
Resources are minimal once replication is setup, during the initial
snapshot, the only issues you might run into are the locking of the tables
as they are processed for replication.
Adam P. Cassidy
"Ryan" <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D4AA35E2-CBA7-4052-93AB-37DF213D729D@xxxxxxxxxxxxxxxx
Paul, thanks a lot!
Do you know any limitation on using transactional replication? eg the min
delay time, can it perform query during the replication.
Aslo how's the overhead on resources of compare to mirroring? Is it
require
many resources (eg. CPU and RAM) during the processing?
Regards,
Ryan
"Paul Ibison" wrote:
Ryan,
transactional replication is often used for this type of reporting
requirement. You could also enhance the system by using the snapshot
committed isolation levels to maintain access while the distribution
agent
is running. The main 'competitor' technology on SQL Server 2005 is
database
mirroring with database snapshots. There's no detailed list of pros and
cons, but as I'm a replication guy I'll point out that mirroring doesn't
support FTI and you can't take back ups of snapshots :)
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
.
- References:
- Database Replication
- From: Ryan
- Re: Database Replication
- From: Paul Ibison
- Database Replication
- Prev by Date: Re: sp_changepublication
- Next by Date: Re: Database Replication
- Previous by thread: Re: Database Replication
- Next by thread: Re: Database Replication
- Index(es):
Relevant Pages
|