Lukas

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Managed Instance  ·  Flag idea as inappropriate…  ·  Admin →
    Lukas supported this idea  · 
  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Lukas supported this idea  · 
  3. 66 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 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.

    Lukas commented  · 

    We got the information that DMS should do the job. The feature should be implemented some time in Q2/Q3. Can you confirm this?

  4. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Managed Instance  ·  Flag idea as inappropriate…  ·  Admin →
    Lukas shared this idea  · 
  5. 48 votes
    Sign in
    (thinking…)
    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 →

    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.

    Lukas supported this idea  · 
  6. 145 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    28 comments  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Lukas supported this idea  · 

Feedback and Knowledge Base