Support tables with same table name but under different scheams in one database.
We are still waiting to see how many people might find this feature useful.
I don't think this needs to be a feature request. It's far too obvious that it should "just work". Two tables with same name, different schema (e.g. dbo.users and dba.users) shouldn't collide (as they obviously don't in the database).
Shane Seibert commented
It has been a very long time since this issue surfaces, however it just hit me today and the only error I was getting is invalid field datatype. The issue is two tables of the same table name but different schema names and the provisioning logic fails. If not supported at least a more appropriate error message about the collision in the datasync schema where the two cannot co-exist by current naming approaches. Maybe include the schema name as fully qualified or give us an option to pick a different scheama.table name when setting up the provisioned side of the sync
Hi Embers, thank you for your feedback. We understand the need to support database schemas for data sync, and we will evaluate its priority as we move sync capability forward. In the short term, we will document this limitation so users are aware that it is not supported at the moment.
This is a fundumental requirement not a feature! It was only after tracking down problems and spending hours reading forum posts did we finally read that - suprisingly - data sync does not support database schemas :/ Basically if you have tables with the same names in different schemas your out of luck. Again with Azure there are all these great features but its the basics / fundumentals that Microsoft falls down on. There is still no reliable way to replicate data to another Azure or on premise DB (Data Sync is still in preview /buggy after 2 years) There is now 'Active Geo-Replication' on the Azure Premium Tier DB's but at £295 + £221 (for the replica) per month its simply not an option on every DB you need to have an up to date copy of to use for reporting or running other services against (you should not be running these against your live db). Either Active Geo-Replication needs to be an option on the Standard Tier or the Azure Team need to fix / develop the Data Sync service and fast. Data replication is a basic requirement that should have been sorted years ago!