Jeff Moden (10/7/2013) GilaMonster (10/7/2013)
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.
Why would that affect the cluster's quorum drive?
Because everything that changes int these tables ends up going to the quorum drive.
If it does someone has badly configured that cluster. There should be nothing from SQL Server on the quorum drive. I don't even know if the quorum drive can be marked as a dependency of SQL, it should be off limits to everything but the cluster management itself.
All that should be on the quorum drive are logs and a few files put down by the cluster installation, it should never be used for anything else.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass