Skip to content

Commit 251faa6

Browse files
John GordonMashaMSFT
authored andcommitted
Adding information about update latency to the firewall page
1 parent cbdab70 commit 251faa6

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

azure-sql/database/firewall-configure.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -259,6 +259,26 @@ az synapse workspace firewall-rule create --name AllowAllWindowsAzureIps --works
259259
| [Delete firewall rules](/rest/api/sql/firewall-rules/delete) | Server | Removes server-level IP firewall rules |
260260
| [Get firewall rules](/rest/api/sql/firewall-rules/get) | Server | Gets server-level IP firewall rules |
261261

262+
## Understanding the latency of firewall updates
263+
264+
The server authentication model has a latency of 5 minutes for all changes to security settings, unless the database is contained and without a failover partner. Changes made to contained databases without a failover partner are instantaneous. For contained databases with a failover partner, each security update is instantaneous on the primary database, but the secondary database can take up to 5 minutes to reflect the changes.
265+
266+
The following table describes the latency of security settings changes based on database type and failover configuration:
267+
268+
| Authentication model | Failover configured | Latency for security settings changes | Latent instances |
269+
|-----------------------|---------------------|--------------------------------------|------------------|
270+
| Server authentication | Yes | 5 minutes | all databases |
271+
| Server authentication | No | 5 minutes | all databases |
272+
| Contained database | Yes | 5 minutes | the secondary database |
273+
| Contained database | No | none | none |
274+
275+
## Manually refreshing firewall rules
276+
277+
If you need to see firewall rules updated more quickly than the 5 minute latency, you can manually refresh the firewall rules. Log into the database instance that needs its rules updated, and run DBCC FLUSHAUTHCACHE. This will cause the database instance to flush its local cache and refresh firewall rules.
278+
```syntaxsql
279+
DBCC FLUSHAUTHCACHE[;]
280+
```
281+
262282
## Troubleshoot the database firewall
263283

264284
Consider the following points when access to Azure SQL Database doesn't behave as you expect.

0 commit comments

Comments
 (0)