June 21, 2002 at 9:32 am
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
June 21, 2002 at 11:20 am
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
June 22, 2002 at 5:11 am
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.
July 1, 2002 at 5:15 am
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)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply