When opting to use a shared Azure SQL database for both SA and MDW (which we are), surely the system can recognise that specific config (from the "duplicate" input by the user) and either demand or automate the creation of schema’s for each DB, and simultaneously also set the “Direct read option” on the SA and MDW DBs to [Matching Server and Database].
If I understand that correctly, this ensures
- that the chance of a table conflict is removed completely, and
- that data moves efficiently between the two DB’s directly in the shared Azure SQL service rather than via ADO.net and the ODX service.
Is there any reason either of those steps couldn’t be automated to mitigate the chance of human error?