locked
Call to SyncScopeProvisioning.Apply times out. RRS feed

  • Question

  • Provisioning my SQL Server 2008 database is consistently timing out with a SqlException while executiong an insert into a tracking table. I retrieved the following statement from a Profiler trace. The base table contains about 25 MB of data and the database is hosted on my laptop.

    INSERT INTO [Sync_Reading_tracking] ([Id], [create_scope_local_id], [local_create_peer_key], [local_create_peer_timestamp], [update_scope_local_id], [local_update_peer_key], [sync_row_is_tombstone], [CustomerId]) SELECT [base].[Id], NULL, 0, @@DBTS+1, NULL, 0, 0, [base].[CustomerId] FROM [Reading] [base] LEFT OUTER JOIN [Sync_Reading_tracking] [side] ON [base].[Id] = [side].[Id] WHERE [side].[Id] IS NULL

    I found the following method is in the stack trace.

    Microsoft.Synchronization.Data.SqlServer.dll!Microsoft.Synchronization.Data.SqlServer.SqlSyncTrackingTableHelper.PopulateFromBaseTable(System.Data.SqlClient.SqlTransaction trans) + 0x3d bytes 

    Am I able to adujst the timeout for the command that is used by this method?

    Update: I was able to provision the database using the script that is returned from the Script method on the SyncScopeProvisioning object.

    Cheers,

    Scott


    MCSD
    Tuesday, December 29, 2009 12:55 AM

Answers

  • Scott, maybe you are also running into this issue that we tracked in this thread: SqlTransaction exception when applying SqlSyncScopeProvisioning for big tables

    Also since you mention that you can run the script and have it working makes me believe it is the same issue. Unfortunately, you have to continue with the workaround and we will fix the issue in the next release.

    This posting is provided AS IS with no warranties, and confers no rights
    • Proposed as answer by Kyle LeckieEditor Wednesday, January 6, 2010 7:43 PM
    • Marked as answer by Scott Munro Wednesday, January 6, 2010 8:03 PM
    Tuesday, December 29, 2009 4:13 AM

All replies

  • Scott, maybe you are also running into this issue that we tracked in this thread: SqlTransaction exception when applying SqlSyncScopeProvisioning for big tables

    Also since you mention that you can run the script and have it working makes me believe it is the same issue. Unfortunately, you have to continue with the workaround and we will fix the issue in the next release.

    This posting is provided AS IS with no warranties, and confers no rights
    • Proposed as answer by Kyle LeckieEditor Wednesday, January 6, 2010 7:43 PM
    • Marked as answer by Scott Munro Wednesday, January 6, 2010 8:03 PM
    Tuesday, December 29, 2009 4:13 AM
  • Hi Mahesh,

    That does look very similar. Thanks for the update.

    Cheers,

    Scott
    MCSD
    Wednesday, January 6, 2010 8:02 PM