September 5, 2023 at 7:21 pm
Hello - over the last few months we have been receiving Semaphore Timeout errors connecting to our Azure VM-based SQL failover cluster. The cluster was built 3 years ago and other than Windows updates, we haven't changed anything configuration wise on these machines.
The errors will originate at all times of the day (e.g. load on the server doesn't appear to be a factor) and occur in a variety of places: SSMS, User Apps and even in SQL Agent jobs.
One troubleshooting option we have on the table is to basically tear down the cluster and Load Balancer, then re-build them. Will the failover instances still exist if we do this?
Option B would be to create a brand-new environment and migrate databases over.
Has anyone run into something similar and is destroying/rebuilding the cluster an advisable/safe thing to do troubleshooting wise?
Thank you.
September 6, 2023 at 8:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply