Skip to content

Commit f60482d

Browse files
Fixed typo
1 parent 96e5d6a commit f60482d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.topic: conceptual
1010
author: dimitri-furman
1111
ms.author: dfurman
1212
ms.reviewer:
13-
ms.date: 03/03/2020
13+
ms.date: 02/03/2021
1414
---
1515
# Azure SQL Database Hyperscale FAQ
1616
[!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -160,7 +160,7 @@ Your database size automatically grows as you insert/ingest more data.
160160

161161
### What is the smallest database size that Hyperscale supports or starts with
162162

163-
40 GB. A Hyperscale database is created with a starting size of 10 GB. Then, it starts growing by 10 GB every 10 minutes, until it reaches the size of 40 GB. Each of these 10 GB chucks is allocated in a different page server in order to provide more IOPS and higher I/O parallelism. Because of this optimization, even if you choose initial database size smaller than 40 GB, the database will grow to at least 40 GB automatically.
163+
40 GB. A Hyperscale database is created with a starting size of 10 GB. Then, it starts growing by 10 GB every 10 minutes, until it reaches the size of 40 GB. Each of these 10 GB chunks is allocated in a different page server in order to provide more IOPS and higher I/O parallelism. Because of this optimization, even if you choose initial database size smaller than 40 GB, the database will grow to at least 40 GB automatically.
164164

165165
### In what increments does my database size grow
166166

0 commit comments

Comments
 (0)