locked
What work does 'SyncSvcUtil.exe' utility do to instrument the database RRS feed

  • Question

  • Microsoft Sync Framework 4.0 provides very good utility 'SyncSvcUtil.exe' to instrument database.

    My client is not comfortable with me instrumenting their production database for Microsoft Sync Framework 4.0? He wants to make sure it will not screw up his production database. 

    If it would be great if anyone can tell me what all operations 'SyncSvcUtil.exe' does to instrument database and if it will hamper database performance in future.

     

    Friday, March 11, 2011 3:22 PM

Answers

  • The only changes that we do to the database when you use SyncSvcUtil is to use the SqlSyncScopeProvisioning/SqlSyncScopeDeProvisioning API's from SyncFx 2.1 to provision/deprovision the database based on the request.

    This means that we create insert/update/delete triggers, tracking tables and few stored procedures per table for change tracking/enumeration/change application purposes. This is exactly similar to what you would have done, had you used SyncFx 2.1 to manually provision the database.


    SDE, Sync Framework - http://www.giyer.com
    • Proposed as answer by Ganeshan Friday, March 11, 2011 6:02 PM
    • Marked as answer by Ganeshan Wednesday, March 30, 2011 11:32 PM
    Friday, March 11, 2011 6:02 PM

All replies

  • SyncSvcUtil is just a utility to provision/deprovision scopes, generate code for WCF-based sync service, isolated store and client entities.

    it's not a utility that's permanently run against the database. the part provision/deprovision part is much like the same provisioning/deprovisioning in v2.1

    perhaps the word "instrument" may be confusing as well.

    Friday, March 11, 2011 4:43 PM
  • The only changes that we do to the database when you use SyncSvcUtil is to use the SqlSyncScopeProvisioning/SqlSyncScopeDeProvisioning API's from SyncFx 2.1 to provision/deprovision the database based on the request.

    This means that we create insert/update/delete triggers, tracking tables and few stored procedures per table for change tracking/enumeration/change application purposes. This is exactly similar to what you would have done, had you used SyncFx 2.1 to manually provision the database.


    SDE, Sync Framework - http://www.giyer.com
    • Proposed as answer by Ganeshan Friday, March 11, 2011 6:02 PM
    • Marked as answer by Ganeshan Wednesday, March 30, 2011 11:32 PM
    Friday, March 11, 2011 6:02 PM