Hey everyone,
Have a question I am hoping someone out here has an idea of.
I have been tasked with upgrading our current MS SQL server to SQL2012 using always on. Now, setting this up, is not a problem. I have done it multiple times and everything for the clustering to the failing over works like a charm. My problem is the program we use does not seem to work after the server has failed over.
The program we use directly connects to the SQL database and manipulates its data. After I have setup AlwaysOn, created the listener, set the IP's and the whole works, the client application connects to the listener, i can do everything i would expect to be able to do, however, when I do a force failover, or purposely take a server down, the client app crashes. When I start it back up again, it continually crashes. This only happens when it cannot connect to the database.
Just to make sure it is not a configuration issue, i have pointed SSMS to the listener and it shows me that it failed over and connects to the right database.
I am thinking, the software we use to access the database is missing some form of code to work with how AlwaysOn works and fails over. Can anyone who has worked with any client application and SQL 2012 AlwaysOn verify this for me?