Skip to content

Commit ce7cd50

Browse files
authored
Merge pull request #88440 from jovanpop-msft/patch-114
Removed iops
2 parents e01b758 + ade5d9f commit ce7cd50

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/sql-database/sql-database-service-tiers-general-purpose-business-critical.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,6 @@ The following table describes the key differences between service tiers for the
4040
| | Managed instance | 32 GB – 8 TB | N/A | 32 GB – 4 TB |
4141
| **TempDB size** | Single database / elastic pool | [32 GB per vCore](sql-database-vcore-resource-limits-single-databases.md#general-purpose-service-tier-for-provisioned-compute) | [32 GB per vCore](sql-database-vcore-resource-limits-single-databases.md#hyperscale-service-tier-for-provisioned-compute) | [32 GB per vCore](sql-database-vcore-resource-limits-single-databases.md#business-critical-service-tier-for-provisioned-compute) |
4242
| | Managed instance | [24 GB per vCore](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) | N/A | Up to 4 TB - [limited by storage size](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) |
43-
| **IO throughput** | Single database | [500 IOPS per vCore](sql-database-vcore-resource-limits-single-databases.md#general-purpose-service-tier-for-provisioned-compute) | Effective IOPs will depend on the workload. | [4000 IOPS per vCore](sql-database-vcore-resource-limits-single-databases.md#business-critical-service-tier-for-provisioned-compute)|
44-
| | Managed instance | [100-250MB/s and 500-7500 IOPS per file](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) | N/A | [1375 IOPS per vCore](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) |
4543
| **Log write throughput** | Single database | [1.875 MB/s per vCore (max 30 MB/s)](sql-database-vcore-resource-limits-single-databases.md#general-purpose-service-tier-for-provisioned-compute) | 100 MB/s | [6 MB/s per vCore (max 96 MB/s)](sql-database-vcore-resource-limits-single-databases.md#business-critical-service-tier-for-provisioned-compute) |
4644
| | Managed instance | [3 MB/s per vCore (max 22 MB/s)](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) | N/A | [4 MB/s per vcore (max 48 MB/s)](sql-database-managed-instance-resource-limits.md#service-tier-characteristics) |
4745
|**Availability**|All| 99.99% | [99.95% with one secondary replica, 99.99% with more replicas](sql-database-service-tier-hyperscale-faq.md#what-slas-are-provided-for-a-hyperscale-database) | 99.99% <br/> [99.995% with zone redundant single database](https://azure.microsoft.com/blog/understanding-and-leveraging-azure-sql-database-sla/) |

0 commit comments

Comments
 (0)