SQL Managed Instance

How can we improve SQL Managed Instance?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Implement Long term backup

    PITR of 35 days is not enough for our production databases.

    We need long-term backup as it's done on Azure SQL Database.

    47 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make managed SQL instance able to access Azure file shares.

    It would be really great if managed SQL instance can access Azure file shares. Many of our Company’s On-Prem SQL applications were using Windows file shares. We had already moved them to IaaS SQL instances.We are not able to migrate all these SQL applications to managed SQL instances from IaaS, due to inaccessibility of Azure file share from managed SQL instance.

    11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 44 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

  4. Support for Kerberos authentication for Linked Servers

    When creating a linked server on a managed instance, the option for login to "Be made using the login's current security context" does not function due to the lack of Kerberos authentication.

    This authentication method is used frequently to allow multiple applications or processes to make use of the same linked server while still restricting the access to the remote server to specific databases on the remote server. For instance, UserA might have access to database A and B through the linked server but UserB only has access to database B.

    Without this support, processes or applications that require SQL…

    13 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Enable Polybase on SQL Managed Instance

    Please enable Polybase on SQL Managed Instance. This will allow us to integrate data from our other IoT Analytic environments (Databrick, and Snowflake) with our corporate data warehouse (SQL MI). Polybase will improve data availability between systems by setting up external tables over Azure Storage Blobs that are shared between systems.

    59 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support for MSDTC

    Many applications need MSDTC including MS apps. Would really like to see this supported in MI.

    38 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for bringing this up. We currently don’t have plans for MSDTC support yet.
    Can you please let us know more about your scenario and how much effort it would take to re-write your application, how big of a blocker it is?

    Implementing MSDTC support in cloud environment is not a trivial ask. We need to make sure that there is a demand for this and it has higher priority than other features.

  7. Make backups portable to on-premise SQL

    Get this message when attempting to restore an SMI backup to on-premise SQL:

    The database was backed up on a server running version 15.00.0700. That version is incompatible with this server, which is running version xx.xx.xxxx. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.

    Lock in is risky for customers for a number of reasons. A workaround is using BACPAC but getting an established database into a state where BACPAC doesn't spew errors is difficult in our experience.

    59 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  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.

  8. Provide higher RAM, lower vCore performance levels

    Often our databases have higher memory requirements, but do not need support for many concurrent connections or levels of parallelism. It would be useful to be able to spec a high memory, low vCore-count system, rather than being forced into a pre-determined ratio.

    18 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  9. Online Managed Instance Scale operations

    Scaling a managed instance takes the instance completely offline which means scaling can only be down during outage windows which defeats the purpose of a PaaS solution. Even scaling storage capacity which is a billing scale up rather than a physical one seems to take the instance down for up to 3 minutes. Then the instance has to start from scratch with query plans and cache.

    Is there no way to have the new instance primed and cut over to rather than killing and starting up from scratch?

    18 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. increase size "managed instance"

    8 TB is currently the maximum capacity of the instance of an Azure SQL DB Managed Instance. This capacity is not sufficient for some scenarios where the volume of data is significant.

    23 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Need to change being Capable to Resize the job history

    SQL agent in SQL MI can keep 10 job history records per each job step and 1000 rows in total.

    If MI can capable to resize job history Log like on-prem SQL, It must be good for CX who has a bunch of scheduled job.
    We can easily imagine If we had 20 jobs which execute every hour, I would be impossible to check the log about the last executed log.

    Also, I think the below link needs to be corrected.
    MI was marked in "APPLIES TO" box.

    So It seems like to capable to resize the job history log.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Linked Server to non SQL Sources

    Allow linked server to non SQL sources - In particular csv and excel.

    30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Managed Instance of SSRS would be great

    A Managed Instance of SSRS to report from a SQL Managed Instance would be ideal. The requirement of having a local (or Azure VM) SSRS server to report against a SQL Managed Instance kind of defeats the purpose of "managed" for those of us who need to generate reports. Power BI does not cut it for the types of reports SSRS can generate.

    28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support for storage endpoints on the same subnet as the SQL managed instance

    there is no support for storage endpoints on the same subnet as the SQL managed instance (forces to disable the firewall for the storage accounts used for db migrations)

    8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Threat Detection Service blocking alter database ... modify filegroup ... command

    While creating a new database on SQLMI using a SQL script generated from SSDT, this command failed:

    ALTER DATABASE [$(DatabaseName)] MODIFY FILEGROUP [BIEN2013] READ_ONLY;

    with this error message:

    Msg 5070, Level 16, State 2, Line 29
    Database state cannot be changed while other users are using the database 'd3b218ed-c416-49c2-bc26-02e915c7e3b6'

    when I looked at the sp_who2 output, I saw that there was a spid from the "TdService" in that DB. Looking this up shows that this is the "Threat Detection Service".

    The spid eventually went away, but this blocked my SSDT deploy.

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable Managed Identity (MSI) Authentication with Managed Instance

    User Assigned Managed Identity and System MSI is supported with SQL DB but not SQL MI.

    See: https://github.com/MicrosoftDocs/azure-docs/issues/23965

    Need to write code "the hard way" to support AAD token auth from code: https://azure.microsoft.com/en-us/blog/securing-azure-sql-databases-with-managed-identities-just-got-easier/

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Make managed instance size more granular

    At the moment with managed instance, the granularity of size is only in 8 core steps. Would be better if it was in 1 or two core jumps with the equivalent cost/memory to better handle scales of different applications. Having to purchase 8 more cores for a an 8 core instance when it needs a little more performance is a big step!

    12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Enable Activity Monitor for managed instance

    The lack of activity monitor and/or via an applet in the portal to see utilization of the pricing level would be most helpful, not just for determining if we need to up size to a higher vcore model but to understand the load on the box by more than just what spid is active (cpu, disk, memory, etc)

    17 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. Provide Option to "Restore a Deleted Database" - the same functionality which is avaialbe in Azure SQL Databases

    Like Azure SQL Databases, provide the option to restore a deleted database in Azure SQL Managed Instance using the portal.

    THe present work-around https://blogs.msdn.microsoft.com/sqlserverstorageengine/2019/01/21/recreate-dropped-database-on-azure-sql-managed-instance/ isn't exactly easy, particularly as SQL DBAs in the organisation I work for , do not have the permissions to do this in the Azure Portal. Furthermore, in the event of an accidental drop; which is quite easy to do in SSMS, including V18.0, the drop confirmation box is not always displayed.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Provide a realistic, functionally equal alternative to SQL profiler if you want to mothball it.

    I would post this in "one of the categories on the right" except that they aren't visible on my mobile.

    Extended events aren't a reasonable substitute for the level of detail profiler can give. I need to be able to run a program and see what queries are executed, what locks are used, etc. I don't need a representative sample or average, that's useless for troubleshooting.

    9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

SQL Managed Instance

Feedback and Knowledge Base