Skip to content

Commit b6f7e8b

Browse files
MashaMSFTMashaMSFT
committed
removing duplicate questions, redirecting to h2 as per dimitri
1 parent f16a687 commit b6f7e8b

2 files changed

Lines changed: 3 additions & 28 deletions

File tree

‎.openpublishing.redirection.azure-sql.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -457,7 +457,7 @@
457457
},
458458
{
459459
"source_path_from_root": "/azure-sql/database/service-tier-hyperscale-named-replicas-faq.yml",
460-
"redirect_url": "/azure/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq",
460+
"redirect_url": "/azure/azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq#read-scale-out-questions",
461461
"redirect_document_id": true
462462
},
463463
{

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

Lines changed: 2 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -428,7 +428,7 @@ sections:
428428
You can connect to these additional read-only compute replicas by setting the `ApplicationIntent` property in your connection string to `ReadOnly`. Any connections marked with `ReadOnly` are automatically routed to one of the HA secondary replicas, if they were added for your database. For details, see [Use read-only replicas to offload read-only query workloads](read-scale-out.md).
429429
430430
- question: |
431-
How do I validate if I have successfully connected to secondary compute replica using SSMS or other client tools?
431+
How do I validate if I have successfully connected to secondary compute replica using SQL Server Management Studio (SSMS) or other client tools?
432432
answer: |
433433
You can execute the following T-SQL query: `SELECT DATABASEPROPERTYEX ('<database_name>', 'Updateability')`. The result is `READ_ONLY` if you are connected to a read-only secondary replica, and `READ_WRITE` if you are connected to the primary replica. Note that the database context must be set to the name of your database, not to the `master` database.
434434
@@ -455,15 +455,13 @@ sections:
455455
- question: |
456456
Can I add indexes and views on my secondary compute replicas?
457457
answer: |
458-
No. Hyperscale databases have shared storage, meaning that all compute replicas see the same tables, indexes, and other database objects. If you want additional indexes optimized for reads on secondary, you must add them on the primary.
458+
No. Hyperscale databases have shared storage, meaning that all compute replicas see the same tables, indexes, and other database objects. If you want additional indexes optimized for reads on secondary, you must add them on the primary. You can still create temporary tables (table names prefixed with # or ##) on each secondary replica to store temporary data. Temporary tables are read-write.
459459
460460
- question: |
461461
How much delay is there going to be between the primary and secondary compute replicas?
462462
answer: |
463463
Data latency from the time a transaction is committed on the primary to the time it is readable on a secondary depends on current log generation rate, transaction size, load on the replica, and other factors. Typical data latency for small transactions is in tens of milliseconds, however there is no upper bound on data latency. Data on a given secondary replica is always transactionally consistent, thus larger transactions take longer to propagate. However, at a given point in time data latency and database state may be different for different secondary replicas. Workloads that need to read committed data immediately should run on the primary replica.
464464
465-
- name: Named replicas
466-
questions:
467465
- question: |
468466
Can a named replica be used as a failover target?
469467
answer: |
@@ -489,29 +487,6 @@ sections:
489487
answer: |
490488
Named replicas will still be available for read-only access, as usual.
491489
492-
- question: |
493-
How do I validate if I have successfully connected to secondary compute replica using SQL Server Management Studio (SSMS) or other client tools?
494-
answer: |
495-
You can execute the following T-SQL query. The database context must be set to the name of the Hyperscale database, not to the `master` database.
496-
497-
```sql
498-
SELECT @@SERVERNAME AS logical_server_name, DB_NAME() AS database_name, DATABASEPROPERTYEX(DB_NAME(), 'Updateability') AS replica_updateability;
499-
```
500-
501-
`replica_updateability` will be `READ_ONLY` if you are connected to a read-only secondary replica, and `READ_WRITE` if you are connected to the primary replica.
502-
503-
- question: |
504-
Can I create any objects or indexes on my secondary compute replicas?
505-
answer: |
506-
No. Hyperscale databases have shared storage, meaning that all compute replicas see the same tables, indexes, views, etc. If you want additional indexes optimized for reads on secondary, you must add them on the primary.
507-
508-
You can still create temporary tables (table names prefixed with # or ##) on each secondary replica to store temporary data. Temporary tables are read-write.
509-
510-
- question: |
511-
How much delay is there between the primary and secondary compute replicas?
512-
answer: |
513-
Data latency from the time a transaction is committed on the primary to the time it is readable on a secondary depends on current log generation rate, transaction size, load on the replica, and other factors. Typical data latency for small transactions is in tens of milliseconds, however there is no upper bound on data latency. Data on a given secondary replica is always transactionally consistent. However, at a given point in time data latency may be different for different secondary replicas. Workloads that need to read committed data immediately should run on the primary replica.
514-
515490
- question: |
516491
How can I improve availability of named replicas?
517492
answer: |

0 commit comments

Comments
 (0)