Support direct upload of bacpac to new or existing database
Please allow us to support a direct upload of a bacpac file both when making a new database or on top of an existing database. Unless there's something I'm missing, to restore on top of an existing database I have to
1) move the bacpac into storage
2) make a new database from storage
3) rename/delete the old
4) rename the new
This process is VERY annoying.
Thanks for your feedback here. Can you please tell me a little more about your scenario here. Is this in Web/Business databases, or V12 and Basic/Standard/Premium?
Francis Ouellet commented
I also have this problem. I using ARM schema template to create à database (Premium P2) and I want to create a flat DB with a bacpac file. It working great when the database does not exist. But when I have already restored the database, IE when I deploy for second time. Azure Resource Management throw error: Exception Microsoft.SqlServer.Management.Dac.Services.ServiceException:Target database is not empty. "The import operation can only be performed on an empty database" and quit.
I using extensions resource nested to a databases resource with storageUri property to a bacpac stored on the artifactsLocation.
I expected that when BD already provisioned ignore the extensions resource.