We do nightly processing for our warehouse data on Server A and we replicate
the data after all the processing to Server B.
What is the fastest way to push this data across ? Right now it seems like
it takes more than an hour to push all the changes across.i.e an hour
latency. We are using trans replication. Any parameters we can tweak to push
the data faster or are there any other techniques.
Please advice.. Thanks
Hassan,
this article quantifies the effects of using most of the available
parameters:
http://www.microsoft.com/technet/pro.../tranrepl.mspx
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||replicate the execution of stored procedures if
1) your stored procedures modify more than one row at a time
2) the bulk of your batch operations use procs
consider using merge replication if
1) your batch operations modify the same row many times, ie a stock market
application.
2) use download only exchangetype
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
Sunday, February 19, 2012
Best way to replicate huge transactions
Labels:
database,
fastest,
huge,
microsoft,
mysql,
nightly,
oracle,
processing,
replicate,
replicatethe,
server,
sql,
transactions,
warehouse
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment