What Events are Triggered by ApplicationTransactionSize

All replies

• 

  

  0

  Sign in to vote

  use ChangesApplied, see: http://blogs.msdn.com/b/sync/archive/2010/09/24/how-to-sync-large-sql-server-databases-to-sql-azure.aspx

  • Marked as answer by Speedware Tuesday, June 19, 2012 4:55 PM

  Monday, June 18, 2012 11:49 PM
• 

  

  0

  Sign in to vote

  June, thanks as always for the excellent information.

  It's a shame that this sort of information is not explicitly identified in the documentation, such as at this page: http://msdn.microsoft.com/en-us/library/microsoft.synchronization.data.dbsyncprovider.aspx which was updated for the new property ApplicationTransactionSize, but not for this important information.

  The functionality here is one more reason for us to press forward upgrading to 2.1 from 2.0. With dozens of applications, hundreds of scopes and thousands of tables, it represents a large undertaking.

  Tuesday, June 19, 2012 4:55 PM
• 

  

  0

  Sign in to vote

  hi steve,

  another interesting point about this property is that almost all docs associates it with synching with SQL Azure, so give me a ping when you get this working on non-Azure setup.

  also, when you do the 2.1 move, will you still use the dynamic filter thing you have before or will you just go for the scope templates this time?

  cheers,

  junet

  Wednesday, June 20, 2012 8:40 AM
• 

  

  0

  Sign in to vote

  June,

  Our thoughts right now on the move to 2.1 is KISS so we're likely to stay with the custom modifications to the central server for the dynamic filtering. It works well, is a known quantity for us and we're well familiar with such things as supporting multiple scope versions at the same time.

  That being said, we'll be investigating all of the functional changes that we know about - know about being the key.

  Steve

  Wednesday, June 20, 2012 12:49 PM