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.100 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This is to announce general availability of 4-Core Managed Instances for Gen-5 hardware:
We have listened, thank you on your patience and for voting on this feature.
Managed Instance Product Group
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.59 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
One of the most wanted Azure SQL Database Managed Instance features is now available!
Check the announcement with link to the docs:
Azure Managed Instance must suport all Collations, not just SQLLatin1GeneralCP1CI_AS Collation40 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.29 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
We are excited to announce availability of the public endpoint for managed instance as of today. More information in this blog: https://techcommunity.microsoft.com/t5/Azure-SQL-Database/Public-endpoint-for-SQL-Database-Managed-Instance-is-available/ba-p/438996
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.22 votes
Thank you for voting for this feature!
Azure AD administrator of SQL Managed Instance now includes sysadmin privileges.
SQL Manged Instance needs to support the same Metric Alerts that SQL Database has.
This is essential to being able to monitor SQL Managed Instance as part of the cohesive alerting setup as our other Azure resources.10 votes
Metrics alerting is now supported from Azure Portal.
Please enable Change Data Capture in Azure SQL.
Very important feature that allows tracking version info about DB tables.10 votes
Thanks for voting for Change Data Capture feature in the Azure SQL DB Managed Instance. it’s been available in SQL MI since its beginning, so you probably wanted to vote for it in other deployment options of Azure SQL DB – single database and elastic pools.
Please condsider using CDC in SQL MI, or vote for adding CDC to the rest of Azure SQL here: https://feedback.azure.com/forums/217321-sql-database/suggestions/9256023-change-data-capture
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.5 votes
Thanks for voting for this feature!
Restoring deleted database within the retention period is now available in Azure SQL Managed Instance.
More details: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-recovery-using-backups#managed-instance-database-1
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.5 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
This feature is now fully supported in Managed Instance: https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-index#new-and-preview-features
"ALTER DATABASE <db name> ADD FILE <logical file name>" doesn't work under specific condition in Managed Instance
I restored to Managed Instance via ".bak" file. this source DB configured some database file.
After restored, I executed
"ALTER DATABASE <db name> ADD FILE <logical file name>",
following error occured.
Unable to open the physical file "https://wasd2p.blob.core.windows.net/managedserver-071/data/829f3544-***_3.ndf". Operating system error 80: "80(The file exists.)".
(if source DB's database file is single, work correctly.)
execute this T-SQL with changing "logical file name",
physical file name's seq number in error message incremented
and finally, it worked.
is this bug ?2 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Thanks for posting this feedback. We assume it’s been caused by a restore bug that is currently fixed. Please let us know if you encounter any other issues.
How long should we expect to wait for approval to participate in the preview. I accepted preview terms two weeks ago and requested an April start. Now we're anxious to kick the tires.2 votescompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Thank you for this feedback.
We had approval mechanism during public preview. Now it’s removed, and SQL MI is in generally available.
Currently I was only able to get SQL MI accepted by a client because for the DR scenario I was able to manually script client initiated backups that backup to geo-replicated blob storage.
SQL MI does support replication to a secondary site but this makes it too expensive for most clients. But they must have a DR solution as the 7-day point-in-time locally redundant backup doesn't meet their security requrement.1 vote
Geo-restore for Azure SQL Database managed instance is available from early 2019.
doc link to dead-endReplication Replication is supported on Managed Instance. For information about Replication, see SQL Server Replication.1 votecompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Thank you for this feedback.
We believe that this has been resolved.
The page https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-vnet-configuration describes a 4 step process
First. Create a Virtual Network Instance
Second. Create a routing table
Third. Add an 0.0.0.0/0 Next Hop Internet route to the table
Fourth: Associate this route with the Virtual Network
That is a lot of friction - why not offer the ability to have steps 2-4 automatically occur?1 votecompleted · AdminSQL Database feature voting forum admins (Product Owner, Microsoft Azure) responded
Thank you for your feedback. We have introduced “Create new VNET” option during provisioning, that would create a compatible VNET during provisioning. Also we created templates for deployment available at here: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-vnet-configuration#create-a-new-virtual-network-for-a-managed-instance
- Don't see your idea?