Answered Error deploy Data Sync

  • Monday, January 09, 2012 6:32 PM
     
     

    Hi,

    I am trying to deploy a Data Sync with only one Table between two database in Azure, and I obtain an Error:

    "Cannot deploy the sync group because one or more tables have a circular foreign key dependency.
    Code: WebUx_CreateSyncGroup_CircularReference
    Tracing Id: dcef5849-2fed-4147-bb86-97b86919baa8"

     

     

All Replies

  • Monday, January 09, 2012 6:43 PM
     
     Proposed
    • Proposed As Answer by Vitor Tomaz Monday, January 09, 2012 6:47 PM
    •  
  • Monday, January 09, 2012 8:38 PM
     
     

    Hello Druibal

    I looked into the tracing ID that you provided. I could see there is a circular dependency between two tables.

    Message=There is a circular dependency between [dbo].[t_Propiedades] and [dbo].[t_Propiedades].

    Currently DSS does not support circular references or self-referencing tables.

    You can also figure out the circular dependency by running the below query in SQL Server Management Studio connecting to your database.

     

    WITH FKCTE(parent_object_id, ObjName, referenced_object_id, Cycle, Path)

    AS

    (SELECT parent_object_id, OBJECT_NAME(parent_object_id), referenced_object_id,

    0,

    CAST('.' + CAST(parent_object_id AS varchar(10))

        + '.' AS varchar(900))

      FROM sys.foreign_keys

    --  WHERE parent_object_id not in (select referenced_object_id from sys.foreign_keys)

     

      UNION ALL

     

      SELECT E.parent_object_id,OBJECT_NAME(E.parent_object_id) , E.referenced_object_id,

        CASE

          WHEN M.Path LIKE

                 '%.' + CAST(E.parent_object_id AS varchar(10)) + '.%'

            THEN 1 ELSE 0

        END,

        CAST(M.Path + CAST(E.parent_object_id AS varchar(10))

               + '.' AS varchar(900))

      FROM sys.foreign_keys AS E

        JOIN FKCTE AS M

          ON E.referenced_object_id = M.parent_object_id

      WHERE M.Cycle =)

    SELECT * FROM FKCTE

     

    Hope this helps.

  • Wednesday, January 11, 2012 5:46 PM
     
     Answered

    Hi

    As Praveen states, we currently do not support circular references between tables or tables that reference themselves.

    In our next update to the service we are adding support the sync of tables that that reference themselves.  Hopefully this will allow your table to be synced.  The next service update will be within a few weeks - watch out for a blog post here - http://blogs.msdn.com/b/sync/

     

    Regards, Mark

  • Monday, March 12, 2012 8:00 AM
     
     

    Hi,

    The error is still there after the latest service update.

    Could you verify that?

    Evgeniy

  • Monday, August 13, 2012 11:36 AM
     
     
    I just verified on the latest Preview (6).  The circular problem is still here.

    Dampee (blog | twitter)


    • Edited by DamPee Monday, August 13, 2012 11:37 AM added link to blog
    •  
  • Friday, November 09, 2012 1:48 PM
     
     

    Mark,  it appears that we're still seeing this issue.  Any ideas as to when this will be resolved?  Or can it be resolved?

    Steve

  • Sunday, November 11, 2012 11:53 AM
     
     
    Steve, Data Sync has been transitted to SQL China team. Let me do some investigation and get back to you later.

    Hope it helps.


  • Wednesday, November 14, 2012 12:34 AM
     
     
    I have confirmed circular reference and self reference are in our backlog. But comparing to other feature requests, we can't give an ETA for them. If you think it's really important, please go to http://www.mygreatwindowsazureidea.com/forums/44459-sql-azure-data-sync-feature-voting to vote for it. Thanks.

    Hope it helps.