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 SQL_Latin1_General_CP1_CI_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 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.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.
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?