Azure Managed Instance must suport all Collations, not just SQL_Latin1_General_CP1_CI_AS Collation29 votes
Thank you for your feedback. We are currently working on supporting instance level collations for Azure SQL Managed Instance.
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.21 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.
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.10 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.
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.7 votes
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.7 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.
Allow linked server to non SQL sources - In particular csv and excel.6 votes
Many applications need MSDTC including MS apps. Would really like to see this supported in MI.6 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.
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.5 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.
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).3 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.3 votes
Thank you for suggestion. We are going to look into this.
PaaS assumes that all updates are good updates. This is not always so. Mistakes are made and functionality is broken during PaaS updates. These are exceedingly painful and disruptive events for production systems. We need to offer 'delay windows' to PaaS instances to provide time to test updates prior to them hitting production instance. A simple mechanism would be to allow choices of 30/60/90 days. Thereby allowing users to establish cascading updates across instances while also ensuring that no instance is ever more than 90-days behind the most recent PaaS software update.3 votes
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.2 votes
Per the documentation for SQL Managed Instances, cross-database queries are supported and one of the reasons you can begin migrating your on prem sql server installations into SQL Manage Instances.
I created a managed instance as well as databases of the appropriate type within the instance, and it did not allow me to query them. When I attempt to query a table from another database, I get the error that it is not allowed in this version of sql.
Please a) fix this, and b) update your documentation as this is not true2 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.2 votes
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.2 votes
My customer ask for a very simple request do you know if it possible to show in MI Overview Blade Private IP of my MI ? We already have fqdn but this will be interesting for my customer to have Private Ip
Thanks for the feedback. All SQL Managed Instances have private ip address. However, they are dynamically allocated. That is why you should always connect using FQDN.
We need to do more to enable very large enterprises to establish, govern and validate the compliance of their PaaS database instances. Enabling a DSC or Group Policy type feature for MI/PaaS that is fully integrated with Azure Monitoring (Service Now) would be a huge win!2 votes
Create a new database using simple syntax:
CREATE DATABASE DBAtools;
And no memory optimized data filegroup is created. However, if you restore a database from an on-premises backup (via blob storage), Managed Instances automatically create a memory optimized data filegroup. This will be problematic since we can never remove that filegroup, and we may not want to use this feature.
To reproduce, I restored several databases like this:
RESTORE DATABASE StackOverflow2010
FROM URL = 'https://stackoverflowbackups.blob.core.windows.net/backups/StackOverflow2010.bak';
We're currently using Azure VMs with SQL Server and love the "WITH FILE_SNAPSHOT" backup option. We're considering a move to MIs in the future, but would love to see this option first.2 votes
Really necessary to be able to port my business critical application to MI. This is a blocker1 vote
- Don't see your idea?