Azure Data Sync: Failed to perform data sync operation: Table do not have clustered index

0
votes

I'm getting the 1: https://i.stack.imgur.com/EiSRL.png

I realize there is an earlier post about this topic with an answer that seems to have been suitable for at least 2 people so far. Azure Data Sync Clustered Index Error

However, I have tried implementing the suggestion and can't get it to accept the non-clustered index on the Azure side to sync. I have tried refreshing the schema on both sides in the Azure tables within the sync group. I tried dropping the tables and letting Azure provision them on its own. Nothing yet has worked for me. Does anyone know if this option should still work or is there something I am overlooking?

HubTableStructure

MemberTableStructure

MemberTestTable

HubTestTable

1
azureazure-sql-databaseclustered-indexnon-clustered-index
Is it possible for you to share the current table structure on both, the hub database and the member database? – Alberto Morillo
What is the data type of the clustered index? It cannot be a uniqueidentifier, for example. Some data types are not supported as clustered index by SQL Data Sync. – Alberto Morillo
I'm not sure exactly what you mean by share the current table structure. If I understand you correctly I drilled down into the tables and provided two snips of a table from the Hub and the member back up in the original question. It seems that the S/O text editor will no allow me to paste a juxtaposition or the two images so sorry about that. Please let me know if this is helpful. – Wuf_fang
Thanks for adding the table structure – Alberto Morillo
I will have to share this with Microsoft Engineers and try get some possible causes and solutions/workarounds. – Alberto Morillo

1 Answers

0
votes

From the images you added to your question we do not see a clustered index created yet. The clustered index is a requirement to use SQL Data Sync.

enter image description here

A Microsoft engineer is asking if you recreated the table with the clustered index on the hub and on the member database. After that he suggest you need to remove the table and then add it back to get the new changes. Or recreate the sync group may be easier.