Here's an interesting one, and hopefully I'm just missing something obvious...
Background:
- 3 node cluster.(A-A-P)
- Windows Server 2008 R2
- SQL Server 2008 R2 Enterprise (SP2)
- Hardware is exactly the same on all 3 physicals.
- SQL Server version is the same on all 3 servers.
Problem:
The other day, we had planned maintenance on all 3 servers. Instance A was on Node B, Instance B was on Node C. Everything was running fine(App wise). We proceeded with the changes to Node A; failed over Instance B from C -> A... and kept going.
As soon as we failed over Instance B from Node C -> A... an application started to get some heavy deadlocking issues. We thought that it was related to our change, but before reverting the changes back, we decided to move the Instance back to its original Node(C) before the problem began. Once the Instance was back on Node C... deadlocking went away.
So my question to you all... are there any server configuration that either reside in the group policy editor, sql, or registry setting etc... that could affect SQL in a negative way? I sp_configured when my Instance was on Node A & C, and the configurations are the same. What am I missing?
Thanks in advance.