It wouldd be great to have smaller instance sizes available - or even a 'basic' tier. this is blocking the route to PaaS at the moment. Most of our customers run on 4/6 cpu cores at most, so cost-wise managed instance is way beyond what is justifiable. Also, its expensive to test. A basic tier would be really useful for POC;s.41 votes
Thank you for your feedback. Yes, we are working on making small size instance available. Also, we are working on dev/test licenses support that would help to test basic scenarios and reduce cost.
Both changes will come in a few months.
Azure Managed Instance must suport all Collations, not just SQL_Latin1_General_CP1_CI_AS Collation34 votes
Thank you for your feedback. Custom collations are currently in public preview: https://docs.microsoft.com/sql/relational-databases/collations/set-or-change-the-server-collation . Currently, you can use PowerShell/Azure ResourceManager template to create an instance with custom collation, while Portal support and more API will be available in January 2019.
GetDate still on UTC all the time. For the promised value of MI to be the destination for lift&shift without code changes, this breaks it. Now developers have to review their code and update it for MI and if decided to move the database to their IaaS environment, they have to change it back again.23 votes
Thank you for your feedback. We are currently working on supporting non-UTC time zone in Azure SQL Managed Instance.
We are also interested in your feedback on use cases for changing time zone setting on the existing instances, aside from the trivial case of correcting time zone chosen by mistake.
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.22 votes
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.
Many applications need MSDTC including MS apps. Would really like to see this supported in MI.15 votes
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.
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.13 votes
It'd be great if this could happen. The idea of integrating an MI with other Azure services via additional virtual machines using on-prem data gateways and self-hosted integration runtimes is not ideal.13 votes
Thank you for this feedback.
We are working on enabling configurable public endpoint for SQL MI. This should be deployed in 2-3 months.
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.8 votes
Allow linked server to non SQL sources - In particular csv and excel.8 votes
It would be idea to be able to pause or suspend the Managed instance during off hours to save on cost7 votes
Having set an Azure AD Administrator account which is an AD Security group. I would like to have functionality included which will allow members to have effectively sysadmin privileges. The whole thought on this would be to allow the AD Admin account the ability to perform more of the day to day DBA activities on all databases.7 votes
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.7 votes
Thank you for suggestion. We are going to look into this.
Enable Multiple read-only secondaries for reporting/geolocation dispersion (assuming business critical tier)
Having multiple read-only secondaries (possibly in other regions) would be useful for reporting-oriented instances.6 votes
Regulators require data to be on-line and query-able for x number of years. However, business value is traditionally gained from data closer to present day. Please enable Stretch DB on SQL MI in order for us to archive old data to a lower performance/high capacity Azure SQL DB. this will allow us to meet regulatory requirements and lower admin overhead for our high value data (that which remains in SQL MI).5 votes
The ability to work with Machine Learning (R Services in particular) is one that is a business driver. Having the Machine learning queries next to the data is something that's required. It was mentioned as being developed in the forums when MI first hit preview. What's the current status?5 votes
Currently with a new Metric Chart (preview) you are dynamically setting the scaling of the chart. We need the ability to set the scale of the chart from 0 to 100% all the time. Look at the attached file. Here are two charts side by side. The scaling is completely different so it makes comparing values between the two charts impossible.5 votes
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.4 votes
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)3 votes
Enabling an option such that Power BI only connects to the read-only instance of SQL Managed Instance for Business tier
Enabling an option such that Power BI only connects to the read-only instance of SQL Managed Instance for Business tier3 votes
I want to change the DB name after restoring the DB and restoring the DB name in order to use the restored DB as the production database.
If the DB name can not be changed, there is a possibility that it is necessary to change the connection string after the DB restore.3 votes
- Don't see your idea?