Skip to content

Commit 4f34656

Browse files
committed
h2 capping consistency
1 parent c2e47b0 commit 4f34656

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Hyperscale provides rapid scalability based on your workload demand.
8686

8787
Provisioning of each of these additional compute replicas can be done in constant time and is an online operation. You can connect to these additional read-only compute replicas by setting the `ApplicationIntent` argument on your connection string to `ReadOnly`. Any connections with the `ReadOnly` application intent are automatically routed to one of the additional read-only compute replicas.
8888

89-
## Deep Dive Questions
89+
## Deep dive questions
9090

9191
### Can I mix Hyperscale and single databases in a single server
9292

@@ -114,7 +114,7 @@ If you are currently running interactive analytics queries using SQL Server as a
114114

115115
If you are running data analytics on a large scale with complex queries and sustained ingestion rates higher than 100 MB/s, or using Parallel Data Warehouse (PDW), Teradata, or other Massively Parallel Processing (MPP) data warehouses, SQL Data Warehouse may be the best choice.
116116

117-
## Hyperscale Compute Questions
117+
## Hyperscale compute questions
118118

119119
### Can I pause my compute at any time
120120

@@ -140,7 +140,7 @@ However, if there’s only one replica, it may take some time to build the local
140140

141141
For mission-critical apps that require high availability with minimal failover impact, you should provision at least 2 compute replicas including the primary compute replica. This is the default configuration. That way there is a hot-standby replica available that serves as a failover target.
142142

143-
## Data Size and Storage Questions
143+
## Data size and storage questions
144144

145145
### What is the maximum database size supported with Hyperscale
146146

@@ -194,7 +194,7 @@ Yes, including row, page, and columnstore compression.
194194

195195
Yes. The data pages associated with a given table can end up in multiple data files, which are all part of the same filegroup. SQL Server uses [proportional fill strategy](https://docs.microsoft.com/sql/relational-databases/databases/database-files-and-filegroups#file-and-filegroup-fill-strategy) to distribute data over data files.
196196

197-
## Data Migration Questions
197+
## Data migration questions
198198

199199
### Can I move my existing databases in Azure SQL Database to the Hyperscale service tier
200200

@@ -279,7 +279,7 @@ Not at this time.
279279

280280
No. The storage format for Hyperscale databases is different from any released version of SQL Server, and you don’t control backups or have access to them. To take your data out of a Hyperscale database, you can extract data using any data movement technologies, i.e. Azure Data Factory, Azure Databricks, SSIS, etc.
281281

282-
## Cross-Feature Questions
282+
## Cross-feature questions
283283

284284
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
285285

@@ -319,7 +319,7 @@ Because the storage is shared and there is no direct physical replication happen
319319

320320
For most performance problems, particularly the ones not rooted in storage performance, common SQL diagnostic and troubleshooting steps apply. For Hyperscale-specific storage diagnostics, see [SQL Hyperscale performance troubleshooting diagnostics](hyperscale-performance-diagnostics.md).
321321

322-
## Scalability Questions
322+
## Scalability questions
323323

324324
### How long would it take to scale up and down a compute replica
325325

@@ -345,7 +345,7 @@ Yes. The `tempdb` database will scale up automatically as the compute grows.
345345

346346
No. Only the primary compute replica accepts read/write requests. Secondary compute replicas only accept read-only requests.
347347

348-
## Read Scale-out Questions
348+
## Read scale-out questions
349349

350350
### How many secondary compute replicas can I provision
351351

@@ -385,6 +385,6 @@ No. Hyperscale databases have shared storage, meaning that all compute replicas
385385

386386
Data latency from the time a transaction is committed on the primary to the time it is visible on a secondary depends on current log generation rate. Typical data latency is in low milliseconds.
387387

388-
## Next Steps
388+
## Next steps
389389

390390
For more information about the Hyperscale service tier, see [Hyperscale service tier](service-tier-hyperscale.md).

0 commit comments

Comments
 (0)