Provide a REST API to allow synchronization status to be monitored programmatically. For example, current status of all Sync Groups to determine if syncs are succeeding or failing for any reason.

Allow on-premises or cloud-based applications to configure sync groups and initiate syncs.

In addition to allowing Sync Group configuration to be updated to cater for schema changes, automatically propagate the schema changes to all databases in a Sync Group.

Add synchronization capabilities for the Windows Azure Blob Service. Allow data to be synchronized between storage accounts and allow on-premises file data to be synchronized with the Blob Service.

When voting for this feature we would appreciate it if you enter a comment with the specific support you require; e.g. sync on-premises SQL Server with a federated database; sync between federated databases; sync reference data between partitions; etc.

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.

Add synchronization capabilities for the Windows Azure Table Service. Allow data to be synchronized between storage accounts and allow on-premises data to be synchronized with the Table Service (from which on-premises stores?).

I don't want the data sync or anything else for that matter to "touch" any of my databases.

Most of the data being passed as datasets is highly compressible. We have created methods to compress/decompress the data when batched, but it would be nice to support this option out of the box to minimize the amount of data being sent over the wire.

support team should get mail notification on failure with required action to be taken to resolve it

Curently if the database contains circular foreign key dependencies the Azure Data Sync will not deploy the sync group reporting the error:
Cannot deploy the sync group because there is a circular foreign key dependency

On-premises SQL Server databases can currently be included in a Sync Group. Would you like support for other databases; if so, which ones?

Allow master and detail relationship to be specified so a filter and the filter value only needs to be present on the master table.

Feature to sync between two database, once they are connected to net or by moving some files to other machine and sync with othere database

Instead, the sync information could be held in a separate database on the same server. This would be great for syncing system critical databases like the SCCM database.

Currently the SQL Azure Data Sync Agent can only connect to one subscription so if you are supporting multiple clients your local server can't participate in multiple sync topologies. The abilty to connect to multiple subscriptions would enable all my client databases to be synced to one management server.

No need to create a _Tracking table in case the Database is read only. This will improve the performance of Data Sync.

Set and forget DB back up to a BLOB in a different Geo location.