Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sourvil
Starting Member
14 Posts |
 Posted - 2009-01-13 : 07:31:45
|
| Hi friends,We have a Merge Replication between Sql Server 2005 Standart Edition (Publisher & Distributor) and Sql Server 2005 Express Edition.We have.net 2.0 application using RMO. (regarding the article http://msdn.microsoft.com/en-us/library/ms146910.aspx)We use Push Subscription method and everything works fine.But in our tests; too much data is transferred between servers before synchronization starts. And i could not find any compress properties on "MergeSubscription" or "MergeSynchronizationAgent" classes.For a 17 column table; if no data is transferred; we have 42kb (Received) and 159kb (Sent) = total 201kb.For a 17 column table; if 100 rows will be transferred, we have 46 + 194 = 240kb totally.I agree that, we have (average) 200kb for default checking any data change. And this is too much for us (because of Satellite connection).Can we use any compression property or any other methods? Or you suggest any other methods?Best regards.. |
|
|
|
|
|
Push Subscription Compress Data