{"id":23336,"date":"2023-03-15T22:12:42","date_gmt":"2023-03-15T21:12:42","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=23336"},"modified":"2023-03-17T10:21:04","modified_gmt":"2023-03-17T09:21:04","slug":"sqlbits-2023-day-1-a-day-with-sql-managed-instance","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sqlbits-2023-day-1-a-day-with-sql-managed-instance\/","title":{"rendered":"SQLBits 2023 -Day 1-A day with SQL Managed Instance"},"content":{"rendered":"\n

Tuesday 14.03.23 was the first day of SQLBits. This day was dedicated to the workshop, and I chose to follow \u201cA Day with SQL Managed Instance\u201d.
During this day, we talked about provisioning, connection and configuration, security, but also data migration and mobility, monitoring, and performance. Last year, Microsoft developers made 42 improvements to the service SQL Managed instance.<\/p>\n\n\n\n

As you can see the day was interesting and we saw a lot of content. So, I am going to give you a summary of the possibilities with Azure SQL Managed instance (SQL MI). Azure SQL Managed Instance uses the most powerful SQL engine (Enterprise Edition) and uses its own VNet. As it is a service that is fully managed by Azure, the person using SQL MI only must implement their own business model. There are two levels of service: the general level for most workloads and the critical level for workloads requiring low latency, memory, or secondary reading.<\/p>\n\n\n\n

\"The
The two differents service tier for SQL Managed Instance<\/figcaption><\/figure>\n\n\n\n

There are still some limitations like backup retention, tempdb etc.
Below is the difference during a failover between the General-Purpose service and the Business-Critical service<\/p>\n\n\n\n

\"Comparision
Comparision between a General-Purpose and business-Critical failover<\/figcaption><\/figure>\n\n\n\n

Provisioning<\/strong><\/h2>\n\n\n\n


Here is what needs to be mentioned to provision the managed instance:
\u2022 Azure Tenant and Subscription
\u2022 Azure VNet and Subnet
\u2022 Resource Group
\u2022 Region
\u2022 Name
\u2022 Admin login name
\u2022 Time zone
\u2022 Collation
After provisioning, it is possible to modify certain options concerning the hardware, the networking, for the maintenance of the window or during a failover. Then, it is possible to modify some options concerning the hardware, the networking, the maintenance window or during failovers.
To create a SQL MI instance in a new subnet, it tooks between 4 and 6 hours before the November 2022 update. Thanks to the 2022 update, the instance is now 30 min long due to the fact Fast provisioning is available to popular configurations that cover most of users (GP, 4 and 8 vCores, default maintenance). For the moment, this new feature is only available for test environments, but should be available this year for the production one.<\/p>\n\n\n\n

Connectivity<\/h2>\n\n\n\n


SQL managed instance integrates into a customer \u2013 owned VNet. Traffic originates from and terminates in a customer\u2019s subnet. The VNet-local connectivity by default, accessible only from within that VNet. SQL managed instance imposes requirementson the subnet for example:<\/p>\n\n\n\n