Lesson Learned #53: Why do you need to use dm_operation_status dynamic management view?

Hello, This week I worked in a new issue that remembered me the importance to use the dynamic management view called dm_operation_status in every operation that I’m doing with any database either Azure SQL Database or Azure SQL Managed Instance. As most probably you know every database creation, modification, deletion, copy , etc.. is asyncronous process,…


Lesson Learned #51: Managed Instance – Import via Sqlpackage.exe doesn’t allow autogrow

Some days ago, I have been working in a service request that our customer faced the following issue: They’ve downloaded the newest version of Sqlpackage.exe tool (18.0) and they’re trying to import a bacpac into their Azure SQL Managed Instance. It has started successfully but it’s hanging while it reaches 32,768 MB size of primary…


Connect to SQL Managed instance

  SQL Managed instance is located inside a Vnet. The options to connect to it are : From the Azure Inside the same VNet (different subnet) From different VNet using VNet peering / Site-to-Site VPN / Express Route circuit (for cross-region connection) From on-premises . Using express Route or VPN Refer to this article for…

0

Lesson Learned #48: Does Azure SQL Database Managed Instance support Resource Governor?

The answer is Yes! and it is great to know. Currently, using Azure SQL Database Managed Instance we could configure a subset of the physical resources of an instance of the Database Engine.  SQL Server Resource Governor, enables us to specify limits on the amount of CPU, physical IO, and memory that incoming application requests can…