SQL Managed Instance

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

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

    We’ll send you updates on this idea

    16 comments  ·  Flag idea as inappropriate…  ·  Admin →

    We are exploring product improvement opportunities in an area of combined relational and non-relational data querying including integration with data lakes and data virtualization from Azure SQL database/Managed Instance to data stored in various formats.
    We are seeking for the customers interested in these new functionalities to participate in the survey below and help us improve our customer experience and product functionalities in Azure SQL DB/MI. If that’s you we are looking for, please fill out this survey: https://aka.ms/sqldbmi-datalake-integration.

  2. Enable pausing Azure SQL DB/Azure SQL Managed Instance

    Enable the ability to pause Azure SQL DB and Azure SQL Managed Instance like what is available in Azure SQL DW or VM.

    Importing/exporting the data is not a viable option for most dev/test environments that need to be started/stopped quickly and easily.

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

    We’ll send you updates on this idea

    14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support DNS aliasing of an Azure SQL Managed Instance (at least for public endpoint)

    As it is already supported for Azure single SQL Database, it would be nice to be able to create an alias for the Managed Instance, especially for the public endpoint address. All clients connecting directly to the public endpoint would be able to use an alias instead of the real name of the instance. Switching instances, disaster recovery, migration scenarios would be a lot easier to handle.
    FYI, creating a public CNAME record redirecting to the public endpoint address of an MI (like instancename.public.***.database.windows.net) does NOT work : IP resolution is good, but no way to login to the instance…

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

    We’ll send you updates on this idea

    planned  ·  10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

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

    We’ll send you updates on this idea

    10 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi all and thank you for your feedback. While this will not directly address backup and restore from MI to back on-premises SQL (this is also being considered and some updates might follow), we are considering a replication technology which might help support this scenario. We are exploring product improvement opportunities in the area of hybrid link using distributed availability groups (AG) replication technology between SQL Server and MI. This will enable near real time data replication between SQL Server and MI. We are also considering failover scenarios both ways. If this might interest you, we invite you to provide your feedback to the engineering team through this online survey: https://aka.ms/mipg-chimera-survey. Thank you.

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

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

    We’ll send you updates on this idea

    14 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Announcing limited public preview availability of LTR backup for up to 10 years for Managed Instance for EA and CSP subscriptions. There are limited number of seats available for whitelisting subscriptions and will be fulfilled on the first come – first serve basis. For customers enrolled, production support will be provided. The feature is now available through PowerShell only. Azure portal should be coming in a few months. To sign up create Azure support ticket: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-long-term-retention#managed-instance-support

    We sincerely appreciate your feedback.
    Managed Instance product group

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

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

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Service Broker between instances

    Azure SQL Managed instance to support Service Broker routing externally between MI's rather than local only.

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

    We’ll send you updates on this idea

    started  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

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

    We’ll send you updates on this idea

    planned  ·  4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support for MSDTC

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

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

    We’ll send you updates on this idea

    9 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Managed Instance engineering team needs your feedback to assess the need for supporting Distributed Transactions scenarios on Azure SQL Managed Instance (SQL MI). We invite you to fill out the following online survey to provide your feedback to us:

    https://aka.ms/sqlmi-distributed-transactions.

    Through filling out the survey, you can also express your interest to participate in a private preview of Distributed Transactions for SQL MI. The survey will take about 10 minutes of your time. We thank you for your participation.

    -Managed Instance Product Group

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

    45 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 →
  11. 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?

    43 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 →
  12. Linked Server to non SQL Sources

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

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

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Increase the number of databases limit

    The current limit of databases in a SQL Managed Instance is 100.
    In our current situation when migration our SaaS products to Azure, we have over 4000 sql databases (one pr customer).

    We would really love to skip managing our SQL VMs ourselves, but we are not really ready for jumping right to Azure SQL and Elastic Pools.

    Our Database Administrators run scripts the old fashioned way and looping through thousands of databases in a script. This is not possible with Azure SQL and Elastic Pools.

    But if we go for SQL Managed Instance, we would get over 40 managed…

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

    We’ll send you updates on this idea

    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support for Proximity placement groups

    We're trying to use SQLDB Managed Instance in a migration from the mainframe.

    We need to do a huge aggregation process on the application VM, but the VM and DB latency is as slow as 1.5 milliseconds, causing performance problems.We also tested it using the Business Critical SKU, but the performance is still lacking.

    If the VM and SQLDB Managed Instance could be set up in the same PPG, this issue could be greatly improved.

    37 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 →
  15. 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.

    29 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 →
  16. Add tagging to database on Azure SQL Managed Instance

    It would be very convenient if it were possible to add tags to the databases that are hosted on Azure SQL Managed Instances. On the Instance level it is possible to add tags, not on the individual Databases.

    Please add this possibility as it will help us with internal invoicing.

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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)

    26 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 →
  18. Option to configure the number of diff backups to take per day to save costs

    Deleting a large amount of data or temporarily enabling a high level of auditing will cause all subsequent diffs before the next full to be significant in size. As designed, I believe that MS takes two diffs a day, so assuming that we are paying per byte stored we are then forced to pay for twice the amount of storage compared to if we could configure the SQLMI to perform only a single diff for that period. By allowing the user to control how many diffs to take the user can better control costs around these times.

    25 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 →
  19. 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)

    23 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 →
  20. Support Merge Replication in Managed Instance

    There are customers and ISV's who have built transactional solutions around Merge Replication and cannot easily rewrite them. ADF does not provide a workaround. This is preventing them from moving to Azure PaaS solution.

    21 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 →
← Previous 1 3 4 5 6 7
  • Don't see your idea?

SQL Managed Instance

Categories

Feedback and Knowledge Base