Skip to content

Commit 820d8c4

Browse files
Added a reference to HS perf article
1 parent 27e81e6 commit 820d8c4

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/sql-database/sql-database-service-tier-hyperscale-faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -314,6 +314,10 @@ No. Compute is decoupled from the storage layer. This eliminates performance imp
314314

315315
Because the storage is shared and there is no direct physical replication happening between primary and secondary compute replicas, technically, the throughput on primary replica will not be affected by adding secondary replicas. However, we may throttle continuous aggressively writing workload to allow log apply on secondary replicas and page servers to catch up, and avoid poor read performance on secondary replicas.
316316

317+
### How do I diagnose and troubleshoot performance problems in a Hyperscale database
318+
319+
For most performance problems, common SQL Server diagnostic and troubleshooting steps should be followed. For Hyperscale-specific diagnostics, see [SQL Hyperscale performance troubleshooting diagnostics](/sql-database-hyperscale-performance-diagnostics).
320+
317321
## Scalability Questions
318322

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

0 commit comments

Comments
 (0)