This appears after failover is complete? I would double check all the configuration and make sure every database you expect is in the AG. Make sure the database is not in recovery.
Hi, Thanks for the response.
Yes, I checked it, once the fail over is complete, all the databases are up sync and available.
Regards
hello -- you might already be aware that the driver they use will have an impact?
But just in case here's the link: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/always-on-client-connectivity-sql-server
e.g.
Driver | Multi-Subnet Failover | Application Intent | Read-Only Routing | Multi-Subnet Failover: Faster Single Subnet Endpoint Failover | Multi-Subnet Failover: Named Instance Resolution For SQL Clustered Instances |
---|---|---|---|---|---|
SQL Native Client 11.0 ODBC | Yes | Yes | Yes | Yes | Yes |
SQL Native Client 11.0 OLEDB | No | Yes | Yes | No | No |
ADO.NET with .NET Framework 4.0 with connectivity patch* | Yes | Yes | Yes | Yes | Yes |
ADO.NET with .NET Framework 3.5 SP1 with connectivity patch** | Yes | Yes | Yes | Yes | Yes |
Microsoft JDBC driver 4.0 for SQL Server |
Check that the app is connecting to the listener, not to the server directly.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
qur7 - Thursday, February 22, 2018 1:45 PM
Hi,
if, as I suspect, the nodes are on different subnets, to get automatic failover you need to ensure that your connection string has the MULTISUBNETFAILOVER=TRUE option is set, and that the driver, and if applicable .NET framework version supports it. If not, then either you have to repoint manually, or it's not going to resolve until after your next DNS refresh
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
Thanks for the feedback.
the two nodes are in the same subnet. I was aware about the different sub-net issue however didn't think it applied in my case.
we resolved the issue. one of the configuration from the application side was using node A server name instead of listener name. once this was corrected, it all worked.
Thanks for the help.
Regards,
qur7 - Tuesday, February 27, 2018 7:06 AM
good to know. checking the connection string was part of my earlier suggestion.
Viewing 10 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply