locked
Can I use Change Data Capture with SyncServices? RRS feed

  • Question

  • I think that it could be used in Sync Services for ADO.NET architecture but I'm not sure if the purpose of CDC is to be used (or have any relation) with Sync Services.

     

    Any suggestion??

     

    thanks!

    • Moved by Max Wang_1983 Friday, April 22, 2011 8:35 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Friday, February 29, 2008 9:19 AM

Answers

  • Jose,

     

    CDC targets ETL and Data Warehousing scenarios whereas Change Tracking targets sync scenarios.  There are quite a few differences between the two including the following:

     

     

    • Scope of Change Type Tracked
      • CT is DML only
      • CDC is DML + some DDL
    • Scope of Changes Tracked
      • CT is net changes only so you are only going to see the most recent version of a record
      • CDC is going to give you every change that has occurred to a given record which is ideal for Slowly Changing dimensions among other things
    • Info Tracked
      • CDC is going to give you the type of DML operation and the changed data
      • CT is going to give you this + transaction info
    • Change Availability
      • CDC will have some latency as it pulls from the transaction log
      • CT happens inline with the actual DML operation
    • SKU of SQL Server
      • CDC availabe in the Enterprise edition only
      • CT available in all SKUs

     

    The latency and asynchronous nature of CDC is generally not ideal for sync scenarios.  I would definitely recommend Change Tracking as this feature is tailored to sync scenarios. 

     

    Sean Kelley

    Program Manager

    Microsoft

     

    Saturday, March 1, 2008 12:20 AM
    Moderator

All replies

  • ...maybe the best choice is "Change Tracking" feature, not CDC. I'm gonna check it up...

     

    Friday, February 29, 2008 11:49 AM
  • Jose,

     

    CDC targets ETL and Data Warehousing scenarios whereas Change Tracking targets sync scenarios.  There are quite a few differences between the two including the following:

     

     

    • Scope of Change Type Tracked
      • CT is DML only
      • CDC is DML + some DDL
    • Scope of Changes Tracked
      • CT is net changes only so you are only going to see the most recent version of a record
      • CDC is going to give you every change that has occurred to a given record which is ideal for Slowly Changing dimensions among other things
    • Info Tracked
      • CDC is going to give you the type of DML operation and the changed data
      • CT is going to give you this + transaction info
    • Change Availability
      • CDC will have some latency as it pulls from the transaction log
      • CT happens inline with the actual DML operation
    • SKU of SQL Server
      • CDC availabe in the Enterprise edition only
      • CT available in all SKUs

     

    The latency and asynchronous nature of CDC is generally not ideal for sync scenarios.  I would definitely recommend Change Tracking as this feature is tailored to sync scenarios. 

     

    Sean Kelley

    Program Manager

    Microsoft

     

    Saturday, March 1, 2008 12:20 AM
    Moderator
  • Thanks Sean!!

     

    This is exactly what I was looking for... now I'm gonna test CT with my running Sync Services apps.

     

    Best regards,,

     

     

    Sunday, March 2, 2008 9:59 AM