Tombstone cleanup failed in Azure data sync log

Anonymous
2020-12-07T02:04:19.55+00:00

Hi there, Pls find following error log in our Azure data sync group. Tracing ID ‘d913edcf-e15d-452f-981d-504fa3bb47f7’ > Tombstone cleanup failed with the exception "SqlException Error Code: -2146232060 - SqlError Number:1205, Message: Transaction (Process ID 64) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. For more information, provide tracing ID ‘d913edcf-e15d-452f-981d-504fa3bb47f7’ to customer support. Meanwhile, we found many oversized side(*_dss_tracking) tables in our db. The performance for sync to on-premise db is also not efficient. Many sync_row_is_tombstone exist in side table. ![45582-image.png][1] [1]: /api/attachments/45582-image.png?platform=QnA

Azure SQL Database
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Navtej Singh Saini 4,216 Reputation points Microsoft Employee
    2020-12-08T03:54:25.06+00:00

    anonymous user

    We have seen this issue previously where there are multiple sync happening and they are conflicting with each other.

    Resolution for this where multiple data sync groups are configured, change the schedule of the data sync which should fix the issue. Please check and convey the same.

    Regards
    Navtej S