Andrew Toi

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Toi commented  · 

    I have been able to verify this behaviour in all versions from SQL2008 thru 2019 CTP2.1 and SQLMI

    Andrew Toi supported this idea  · 
  2. 442 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  31 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Toi supported this idea  · 
  3. 7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Managed Instance  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew Toi shared this idea  · 
  4. 77 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Thank you for your feedback. Yes, we are working on making small size instance available which will considerably reduce the cost. This change will come in a few months.
    At this time if you are using MSDN (developer) type of subscription, a discounted price to provision Managed Instance is automatically applied. Thank you.

    Andrew Toi supported this idea  · 
  5. 40 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Andrew Toi supported this idea  · 

Feedback and Knowledge Base