Skip to content

Commit e9d7fd3

Browse files
Merge pull request #37879 from mokabiru/patch-3
Update sql-database-service-tier-hyperscale-faq.md
2 parents 436ac37 + 7694bf2 commit e9d7fd3

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -356,6 +356,12 @@ We create 2 replicas for Hyperscale databases by default. If you want to adjust
356356

357357
You can connect to these additional read-only compute nodes by setting the `ApplicationIntent` argument on your connection string to `readonly`. Any connections marked with `readonly` are automatically routed to one of the additional read-only compute nodes.
358358

359+
### How do I validate if I have successfully connected to secondary compute node using SSMS / other client tools?
360+
361+
You can execute the following T-SQL query using SSMS / other client tools:
362+
`SELECT DATABASEPROPERTYEX ( '<database_name>' , 'updateability' )`.
363+
The result is `READ_ONLY` if you your connection is pointing to the read-only secondary node or `READ_WRITE` if your connection is pointing to the primary node.
364+
359365
### Can I create a dedicated endpoint for the read-scale replica
360366

361367
No. You can only connect to read-scale replica by specifying `ApplicationIntent=ReadOnly`.

0 commit comments

Comments
 (0)