locked
using MSF 2.0 CTP2 , what is the replacement for ‘SqlExpressClientSyncProvider’ ? RRS feed

  • Question

  • In CTP2, Does SqlSyncProvider replace  ‘SqlExpressClientSyncProvider’  for the Client Sync Adapter  (syncagent local provider) ?
    If not , what client sync adapter should I use  (I am using n-tier hub and spoke, with Sql 2005 on server and sql 2005 (express) on the client )
    ------------------------------------------------------------------------------------------------------------
    I am seeing errors like this :

    'Microsoft.Synchronization.Data.SqlServer.SqlSyncProvider' does not contain a definition for 'SelectNewAnchorCommand' and no extension method 'SelectNewAnchorCommand' accepting a first argument of type 'Microsoft.Synchronization.Data.SqlServer.SqlSyncProvider' could be found (are you missing a using directive or an assembly reference?)  

    The samples under Microsoft SDKs\Microsoft Sync Framework\v2.0\Samples seem to be limited to NTFS sync.
    Is there a SqlSyncProvider example I can look at ?
    --------------------------------------------------------------
    Background : Previously, I used  ‘SqlExpressClientSyncProvider’  which I got from here :http://code.msdn.microsoft.com/sync/Release/ProjectReleases.aspx?ReleaseId=1200
    But SqlExpressClientSyncProvider   does not implement CreateSchema, and which means I cannot use TruncateExistingOrCreateNewTable in my snapshot.
    Thanks a ton,
    Peter

     

     

    • Moved by Hengzhe Li Friday, April 22, 2011 1:58 AM (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Thursday, August 6, 2009 10:23 PM

Answers

  • Kind of. As you know the hub spoke proviers are not based on MSF. We decided to make efforts on extending capabilities of the peer providers. With the CTP2 of MSF V2, we have shipped providers for CE adn Sql server. Inface we have also shippied provisioning API's that automates the process of provisioning your Sql server with all related schema changes. The work involved in bootstrapping a Peer to peer solution in CTP2 is very limited.
    Maheshwar Jayaraman - WCF -- http://blogs.msdn.com/dotnetremoting
    Tuesday, August 11, 2009 7:15 PM
    Moderator

All replies

  • Peter,
    SqlSyncProvider is a complete peer provider implementation for the Sql Server (Express/enterprise) SKU. It is not the hub-spoke provider. Infact there is no new changes in the hub-spoke providers in this CTP. We highly recommend using the new peer providers to achieve synchronization.


    Maheshwar Jayaraman - WCF -- http://blogs.msdn.com/dotnetremoting
    Friday, August 7, 2009 4:21 AM
    Moderator
  • Maheshwar,

    Converting from hub & spoke to peer to peer is a big amount of work for me .

    Why don't we have a SQL Client Sync Provider for hub & spoke ?Is the strategic direction of MSF towards peer to peer?

    Thanks,Peter
    Friday, August 7, 2009 3:44 PM
  • Kind of. As you know the hub spoke proviers are not based on MSF. We decided to make efforts on extending capabilities of the peer providers. With the CTP2 of MSF V2, we have shipped providers for CE adn Sql server. Inface we have also shippied provisioning API's that automates the process of provisioning your Sql server with all related schema changes. The work involved in bootstrapping a Peer to peer solution in CTP2 is very limited.
    Maheshwar Jayaraman - WCF -- http://blogs.msdn.com/dotnetremoting
    Tuesday, August 11, 2009 7:15 PM
    Moderator