I'm with Karl et al, any kind of progress indicator to help us make an estimate, track progress. The business counts on us and all we can tell them is "I started a restore and it appears to still be running." Of course, we are doing a restore, and we are probably all needing something out of it and being blind to its progression is a substantial detriment.
Azure SQL Analytics provides this information today. There is also SCOM MP available, and third party solutions such are SentryOne and Red Gate.Shane Seibert shared this idea ·
We are still waiting to see how many people might find this feature useful.
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
Data Sync team is planning to improve initial synchronization performance by using bulk insert and other optimization techniques.
We hear you. This is a common ask and we will consider this going forward.
158 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is not currently planned at this time. Will keep this item open for voting and comments.
This would be a huge improvement on our ability to adopt PAAS db's for our portal implementation with power_bi. We need multiple DBs for assembly vs direct-query targets and getting the data from one to another after it's assembled would be much simpler with this.