Author: Sean Gallardy

Using Distributed Network Names with Availability Groups

I’ve been asked this question a few times, so I feel it’s worth writing about, which is, “Are Distributed Network Names (DNN) supported for SQL Server?”. The short version is, it’s not supported. The long version is, it’s not supported, but if you’re using a vanilla AG (not distributed) and aren’t using things like replication […]

Read article: Using Distributed Network Names with Availability Groups

Attempting to recycle all monitors that have loaded the DLL sqsrvres.dll or hadrres.dll and you notice a SQL FCI/AG failed health checks

I won’t say I told you so… I will, however, point out common AG question #8… I’m not sure why so many of these are coming up lately, but I’ve not had to troubleshoot a few, and I think it’s worth documenting this behavior. Let’s say you have Windows cluster which might have FCI’s, AG’s, […]

Read article: Attempting to recycle all monitors that have loaded the DLL sqsrvres.dll or hadrres.dll and you notice a SQL FCI/AG failed health checks

Top Asked Availability Group Questions… and Maybe Some Helpful Tidbits as Answers

This is inspired by all the times I am forced to repeat myself. To cut down on hearing my own horrible sounding voice, I present to you a FAQ style post of all things Availability Group related that I am consistently asked. Last updated June 25th, 2020. Q1: What’s the limit of databases I can […]

Read article: Top Asked Availability Group Questions… and Maybe Some Helpful Tidbits as Answers

Error 35217 And Availability Groups /SMH

Well That Escalated Quickly… Error 35217 translates to, “The thread pool for AlwaysOn Availability Groups was unable to start a new worker thread because there are not enough available worker threads. This may degrade AlwaysOn Availability Groups performance. Use the “max worker threads” configuration option to increase number of allowable threads.” which is fairly fatal […]

Read article: Error 35217 And Availability Groups /SMH

Stop using Sys.dm_hadr_cluster_members for “quorum” information

Update 5/24/2022: I’ve updated the DMV to reflect the various node and witness dynamic settings with a new column at the end of the DMV called number_of_current_votes. This is only in 2022 and will not be backported. Background I’ve now run across a few different instances where the monitoring for quorum was done via this […]

Read article: Stop using Sys.dm_hadr_cluster_members for “quorum” information

SQL Server Self-Signed Certificate “Vulnerabilities”– FFS Get Off My Lawn

Refresher It may be news (or not) to you that SQL Server can utilize the latest transport security standards when talking to clients and servers. Normally you’d need to create your own certificate for use with said standard protocols, but SQL Server is super nice and will create one for you, self-signed, and use that […]

Read article: SQL Server Self-Signed Certificate “Vulnerabilities”– FFS Get Off My Lawn

Error 8474 state 11, 17836 state 20, 9642 state 3, and your company’s need to incessantly scan for vulnerable ports

The road to Hell is paved with good intentions. I get it, your security team is the best ever. You work at a company where the industry (or public sector) requires that servers be “compliant” by constantly and incessantly scanning them for vulnerabilities, in production of course. I know for some it checks a required […]

Read article: Error 8474 state 11, 17836 state 20, 9642 state 3, and your company’s need to incessantly scan for vulnerable ports