Hi everyone,
We have a SQL replication that moves a large amount of data between our
administration site and a production eCommerce platform at our hosting
provider. The hardware at either end isn't especially taxed on either the
source cluster or the destination cluster and bandwidth shouldn't be an issue
either as we have a 9Mbps pipe at HQ and the hosting provider has MUCH more
available.
The problem is that this synchronization job is taking a huge amount of time
as I see the replication traffic move at a rate of 25Kbps to 250Kbps.
Because of the locks that the import imposes, this has the effect of shutting
the site down.
I realize that this isn't the best designed site and that there are better
ways to do this, but we have inherited this site and have to keep it working
until the redesigned pieces can be moved into production... near the top of
the list is fixing this.
I am open to suggestions; please help.
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
Please take a look at this article for optimisation posibilities:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
HTH,
Paul Ibison
Friday, March 30, 2012
Replication Throughput
Labels:
amount,
database,
ecommerce,
microsoft,
moves,
mysql,
oracle,
ouradministration,
platform,
production,
replication,
server,
sql,
throughput
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment