We ahev setup a SQL Server (64-bit) Failover Environment which consist of a Node A (active) and Node B (passif).
The setup was completed successfully and was working fine since june 2008.
Our system administrators have reported that, after they made some changes during a maintenance week-end, the SQL Server Services don't start anymore on the node B (even though they turn off the active node A and make Node B as active). Our attempts to manuallyÃÂ start those services arealways failing.
Can someone help?
View Complete Post