January 18, 2025 at 12:50 am
Hello!
SQL Clustered resource used to come online during manual or automatic failover in less than a minute but now it is taking about 3-5 mins.
What could be causing it?
Thanks in advance.
January 18, 2025 at 3:45 pm
Depends on the resource - if it is SQL Server installed into the cluster, the delays could be caused by how long it takes SQL Server to start and recover all databases. For that - if you have transaction log files with a lot of VLF's that have data in them that needs to be rolled forward and rolled back that will take additional time.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 29, 2025 at 8:59 am
Jeffrey is definitely on to something.
You can check this by looking at the SQL log on the node that is starting up, this will tell you how long it is taking for SQL to get to a ready status, and what is happening before that. There should be hardly a second between SQL being ready and the resource coming online.
Another possibility is some sort of delay in moving resources to the passive node. Keep a note of how long it takes each resource to come online. SQL cannot start it's own startup until all dependant resources are online.
When you know what is causing the delay, the fun bit starts as you look at how to minimise it. Good luck with that.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply