There were a few emails about login times so I figured it warranted a blog post. Strap in, this one goes sideways fast. Some people noted that the amount of time to log in with a SQL Login in SQL Server 2025 all of a sudden took longer. This is clearly stated in the Docs, […]
I have a long history shitting on CrowdStrike – and well, with their past it’s pretty warranted – but antivirus software is general does bother the hell out of me. You’re essentially installing something that interrogates everything on your system and injects itself everywhere hoping it stops a known issue but generally ends up causing […]
Primer If you haven’t already read up on cooperative and preemptive scheduling or aren’t sure what those are, please read the intro to that first, otherwise you’ll be lost. Much as I’ve discussed before, SQL Server uses a cooperative scheduling model. This doesn’t mean that Windows does, nor does it mean Windows will scheduler whatever […]
Issue Introduction In this olved stery the problem comes as a slow database restore. That’s what I was given, that’s all I have. It’s super fun when someone tells you the issue and there is absolutely no information or data around it, right? Questions That Need Answered Why is the “restore slow” What factors, if […]
You’ve won! If, somehow, you’ve managed to see this error in your errorlog then congratulations, you’ve won an instance of SQL Server that probably won’t be doing much. I found out about this message a few months ago, but it has been in the product for years and I went this long without ever even […]
One of the most common issues I look at from day to day is some variation of the question. “Why did it take a long time for my AG/Database to failover?”. There are many different meanings for this innocuously simple looking statement, for example was it that the failover time was long or was it […]
I tend to be involved in many HA related issues, as is the nature of my current work agreement. The interesting part is that roughly 85% of all the “HA” issues are performance issues (with 10-12% being config issues and the last 3-5% being truly HA issues). Whether this is an FCI, AG, Replication, some […]
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 […]
