You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ Hyperscale provides rapid scalability based on your workload demand.
86
86
87
87
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.
88
88
89
-
## Deep Dive Questions
89
+
## Deep dive questions
90
90
91
91
### Can I mix Hyperscale and single databases in a single server
92
92
@@ -114,7 +114,7 @@ If you are currently running interactive analytics queries using SQL Server as a
114
114
115
115
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.
116
116
117
-
## Hyperscale Compute Questions
117
+
## Hyperscale compute questions
118
118
119
119
### Can I pause my compute at any time
120
120
@@ -140,7 +140,7 @@ However, if there’s only one replica, it may take some time to build the local
140
140
141
141
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.
142
142
143
-
## Data Size and Storage Questions
143
+
## Data size and storage questions
144
144
145
145
### What is the maximum database size supported with Hyperscale
146
146
@@ -194,7 +194,7 @@ Yes, including row, page, and columnstore compression.
194
194
195
195
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.
196
196
197
-
## Data Migration Questions
197
+
## Data migration questions
198
198
199
199
### Can I move my existing databases in Azure SQL Database to the Hyperscale service tier
200
200
@@ -279,7 +279,7 @@ Not at this time.
279
279
280
280
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.
281
281
282
-
## Cross-Feature Questions
282
+
## Cross-feature questions
283
283
284
284
### Do I lose any functionality or capabilities after migration to the Hyperscale service tier
285
285
@@ -319,7 +319,7 @@ Because the storage is shared and there is no direct physical replication happen
319
319
320
320
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).
321
321
322
-
## Scalability Questions
322
+
## Scalability questions
323
323
324
324
### How long would it take to scale up and down a compute replica
325
325
@@ -345,7 +345,7 @@ Yes. The `tempdb` database will scale up automatically as the compute grows.
345
345
346
346
No. Only the primary compute replica accepts read/write requests. Secondary compute replicas only accept read-only requests.
347
347
348
-
## Read Scale-out Questions
348
+
## Read scale-out questions
349
349
350
350
### How many secondary compute replicas can I provision
351
351
@@ -385,6 +385,6 @@ No. Hyperscale databases have shared storage, meaning that all compute replicas
385
385
386
386
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.
387
387
388
-
## Next Steps
388
+
## Next steps
389
389
390
390
For more information about the Hyperscale service tier, see [Hyperscale service tier](service-tier-hyperscale.md).
0 commit comments