SQL 2005 in an Active/Passive Cluster

  • We are currently running SQL 2005 in an Active/Passive Cluster environment. The issue we are having is that when the active node fails over to the passive node, the database connection to the client application disconnects and does not reconnect unless the user logs in again and reruns the failed process. The client application in this case is PeopleSoft. Does anyone know if this is the expected behavior or is there a setting within the cluster administrator or SQL that will prevent this from occurring? Or perhaps this is a setting within the client application? Any information would be greatly appreciated!

    Thanks!

  • this would be a client setting, not sure on where it is set for peoplesoft, may not be an option in that particular application.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply