48 votesneed-feedback · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is a difficult one to handle technically. However the main theme is cost savings. Are there other cost-saving options (other than pausing) that could address this concern? For example, smaller vCore Managed Instances etc.? On the other hand, implementing pausable Managed Instance can also mean that resuming them will take several hours each time. Is this a concern? Thank you.Brad commented
Also providing feedback...
Our use case is for dev/qa environments where we do not need them powered on when our dev team is not working. Taking several hours to resume would not be ideal unless we could schedule it to be fully resumed by a certain time in the morning (provided we aren't charged for the startup time or else the cost savings would be gone).
Yes - cost savings is the motivator, so this could be addressed via licensing as well (free dev/qa instances for MSDN subscribers and/or Enterprise customers, etc). Not sure how well smaller vCore instances would work for *this* concern, I would have to see what's possible with it. Could we automate the scale down / scale up the vCores quickly? How much cost would it save scaling them down overnight?
4 votesBrad shared this idea ·
66 votesunplanned · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Thanks for the feedback.
We assume that you are talking about ability to restore native backup (.bak files) taken from SQL MI to SQL Server 2017/2019.
It’s a tough one unfortunately. Native backup contains binary data, and never been backwards compatible. E.g. you can’t restore backup from SQL 2012 on SQL 2008. Same logic applies here.
SQL MI gets updates faster SQL Server, as soon we check-in code, it gets deployed with the next wave of updates on Azure. Same as SQL DB.
Theoretically if you take backup of SQL MI now, and wait until SQL Server version release catch up, then you will be able to restore it.
Can you please let us know what kind of issues with BACPAC you are encountering?
Also, you can consider making transaction replication from SQL MI on on-prem as a way to move data around.Brad commented
Our use case for this request would be to be able to restore an archived backup of a database from within the past 3-7 years to be able to answer auditing questions. We would prefer not to have to create a new managed instance for this. Transaction replication would not work, BACPAC might work but is not ideal.
4 votesneed-feedback · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Importing a BACPAC to Managed Instance is already supported. Please try it using the latest SSMS/SSDT/SQLPackage and let us know if something is still missing.