Support for tables for which primary key is different than Clustered index
In a lot of situations the Clustered index differs from the primary key in a table. At this moment, Data Sync supports only tables for which the clustered index is the primary key. It would be nice if this restriction is not needed. This will make live much easier to sync data between on-premise and SQL Azure db. We can't change current datamodel in our application. Current datamodel is made based on performance.
Thanks for the suggestion! We are evaluating the priority and cost for implementing this.
Absolutely, on one hand you suggest having Guids as PKs and removing the clustered index from them, on other hand this is not supported on Data Sync.
Seems like it is impossible to have a combination of Sql Azure + Federations + Data Sync that actually performs. (Assuming Data Sync will ever support Federations)