Largest Replicated Database

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Replication » Largest Replicated Database

Largest Replicated Database

Rate Topic

Display Mode

Topic Options

Author

Message

Rob DeMotsis

Posted Friday, June 21, 2002 9:32 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 31, 2005 7:25 PM
Points: 49, Visits: 1

What is the largest database any of you have ever replicated?

Rob DeMotsis
Sr. SQL Server DBA
Pier 1 Imports, Inc.

Rob DeMotsis
Sr. SQL Server DBA

Post #4970

Andy Warren

Posted Friday, June 21, 2002 11:20 AM

SSCertifiable

Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462, Visits: 1,384

5g or so. Only time the size matters is if you're doing a snapshot. Across a slow link it can take a while! You can always work around that issue. Besides that the other consideration is going to be how many trans per sec you have to support and what kind of latency you have.

Andy
http://www.sqlservercentral.com/columnists/awarren/

Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter

Post #36126

Nick Beagley

Posted Saturday, June 22, 2002 5:11 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Sunday, November 25, 2012 3:50 PM
Points: 587, Visits: 251

20 Gig - Transactional replication.

As Andy said it's the snapshot that's the problem. BCPing all the data. If you can afford a small downtime on your publisher you may be better to establish the subscription with @sync_type = 'NONE' and then backup-restore to the other server (or log ship to it to minimise downtime), rename the database, truncate all the tables on your subscriber that you aren't interested in, and then kick off your @sync_type = 'NONE' subscription.

Thinking about it now you don't really have to have a downtime on your publisher. You can just let the subscription fail because there's no database there (or stop it before it does), and your transactions can build up in the distributiondb while you setup the subscriber.

Post #36127

Neil S Hambly

Posted Monday, July 01, 2002 5:15 AM

Grasshopper

Group: General Forum Members
Last Login: Wednesday, October 06, 2004 7:32 AM
Points: 20, Visits: 1

Overall my largets DB is around 30GB (Transactionally) with one of the tables over 8GB on it'd own, it really depends on the overall Transactions.
Only had a couple of Problems when Timeouts had occurred and this stops replication when it is trying to apply a command IE Delete when the operation ahs already occurred. usually just a case of removing the commands for that article and then redoing the original steps and letting replication start over again.
Overall my I/O's todate for the Subscriber/Source Database is presently over 2TB(yes 2000 GB of I/O's)

Post #36128

« Prev Topic | Next Topic »

Permissions