Essentially, DBCC FLUSHAUTHCACHE empties the database authentication cache containing details about logins and firewalls. This is not applicable for the on-premises databases or stand-alone SQL Server installation.
This is required in the Azure SQL Database because in Azure when a password is reset in SQL Database, the connection won’t be unauthenticated. However, in the case of the on-premises database, if the password has changed since the connection was initially authorized, the connection must be terminated and a new connection made using the new password.
If you want to remove the cache in Azure which saves details about the password, you can run the following command.
Here are my few recent videos and I would like to know what is your feedback about them. Do not forget to subscribe SQL in Sixty Seconds series. I hope you appreciate learning about the Last 5 SQL in Sixty Seconds Video.
- Generate Script of SQL Server Objects – SQL in Sixty Seconds #184
- Prevent Unauthorized Index Modifications – SQL in Sixty Seconds #183
- MAX Columns Ever Existed in Table – SQL in Sixty Seconds #182
- Tuning Query Cost 100% – SQL in Sixty Seconds #181
- Queries Using Specific Index – SQL in Sixty Seconds #180
- Read Only Tables – Is it Possible? – SQL in Sixty Seconds #179
- One Scan for 3 Count Sum – SQL in Sixty Seconds #178
- SUM(1) vs COUNT(1) Performance Battle – SQL in Sixty Seconds #177
- COUNT(*) and COUNT(1): Performance Battle – SQL in Sixty Seconds #176
If you have any questions, you can always reach out to me on Twitter.
Reference: Pinal Dave (http://blog.SQLAuthority.com)