My feedback

  1. 77 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SQL Managed Instance  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    Steve commented  · 

    Or the option or opportunity to upgrade on premise version to match the MI version. Some off MI platform development, POCing, and testing is useful.

  2. 283 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Storage » Managed Disk Storage  ·  Flag idea as inappropriate…  ·  Admin →
    Steve supported this idea  · 

Feedback and Knowledge Base