Skip to content

Commit 4e1ad0e

Browse files
authored
Merge pull request #46414 from srdan-bozovic-msft/master
subnet size estimate that includes Business Critical tear
2 parents 158b2ca + 0720605 commit 4e1ad0e

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/sql-database/sql-database-managed-instance-vnet-configuration.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,8 +54,9 @@ If you plan to deploy multiple Managed Instances inside the subnet and need to o
5454

5555
- Azure uses five IP addresses in the subnet for its own needs
5656
- Each General Purpose instance needs two addresses
57+
- Each Business Critical instance needs four addresses
5758

58-
**Example**: You plan to have eight Managed Instances. That means you need 5 + 8 * 2 = 21 IP addresses. As IP ranges are defined in power of 2, you need the IP range of 32 (2^5) IP addresses. Therefore, you need to reserve the subnet with subnet mask of /27.
59+
**Example**: You plan to have three General Purpose and two Business Critical Managed Instances. That means you need 5 + 3 * 2 + 2 * 4 = 19 IP addresses. As IP ranges are defined in power of 2, you need the IP range of 32 (2^5) IP addresses. Therefore, you need to reserve the subnet with subnet mask of /27.
5960

6061
## Create a new virtual network for Managed Instances
6162

0 commit comments

Comments
 (0)