Thank you for your feedback! We will consider this request as we priority our feature backlog.
I'd also like to add GEOGRAPHY to this list. I can't sync my database due to the following error:
Database provisioning failed with the exception "Column 'GeographyDefinition' in table 'dbo.GPSData' is of a type that is invalid for use as a key column in an index or statistics.
Inner exception: SqlException Error Code: -2146232060 - SqlError Number:1978, Message: Column 'GeographyDefinition' in table 'dbo.GPSData' is of a type that is invalid for use as a key column in an index or statistics.
For more information, provide tracing id ‘f89f858b-ae87-4053-ba69-13174c88e20b’ to customer support.
Right now I have to run an on-prem sql server with SSIS to perform the data loads. I'd like an option to host this in Azure.
Given that most Windows Azure SQL Database customers are now advised to use with custom sharding pattern for scale-out, we are re-evaluating when you would want to use sync for a sharded environment – is it syncing from on-prem SQL Server to multiple shards in the cloud, synchronizing between the shards in the cloud, or syncing from multiple shards down to on-prem SQL Server? We’d appreciate your input on this.
I'd also like to see data sync between two federated database instances. That way I can set up a multi-region availabiltiy group.
Thanks for the feedback, we are working on better compatibility between SQL Server and SQL Database in the table fragmentation area.