Hi everyone,
Currently I am exploring and testing out this new feature (AlwaysOn) in SQL Server 2016 Standard Edition since Microsoft unlock this feature in standard edition but with limitation.
Here's the settings that I did and I already point the SQL connection to SQL cluster node in my application using ODBC :-
SQL Servers : SQL2016-1 (Primary server) , SQL2016-2 (Secondary server) and both servers are virtual machines but in different host machines.
Cluster SQL Server : SQL2016-C
Numbers of Availablity Groups : 4 (since I have 4 databases)
Next, I encounter some connection issues when I open my application, mentioned that the database is not available.
----------------------------
Scenario 1 :-
I open 'Failover Cluster Manager' and check SQL2016-C that the current host server is on SQL2016-1 , but the databases already failover to SQL2016-2, vice versa. End up I have to manual failover
----------------------------
Scenario 2 :-
I open 'Failover Cluster Manager' and check SQL2016-C that the current host server is on SQL2016-2 , but the databases remains at SQL2016-1, vice versa.
---------------------------
End up I have to manual failover repeatedly. Does anyone encounter such problem before on standard edition? Is there any extra configuration needed. Hope can get some advice here, else I am unable to move on from database mirroring.
Many thanks and have a nice day.
Best Regards,
Harn
Currently I am exploring and testing out this new feature (AlwaysOn) in SQL Server 2016 Standard Edition since Microsoft unlock this feature in standard edition but with limitation.
Here's the settings that I did and I already point the SQL connection to SQL cluster node in my application using ODBC :-
SQL Servers : SQL2016-1 (Primary server) , SQL2016-2 (Secondary server) and both servers are virtual machines but in different host machines.
Cluster SQL Server : SQL2016-C
Numbers of Availablity Groups : 4 (since I have 4 databases)
Next, I encounter some connection issues when I open my application, mentioned that the database is not available.
----------------------------
Scenario 1 :-
I open 'Failover Cluster Manager' and check SQL2016-C that the current host server is on SQL2016-1 , but the databases already failover to SQL2016-2, vice versa. End up I have to manual failover
----------------------------
Scenario 2 :-
I open 'Failover Cluster Manager' and check SQL2016-C that the current host server is on SQL2016-2 , but the databases remains at SQL2016-1, vice versa.
---------------------------
End up I have to manual failover repeatedly. Does anyone encounter such problem before on standard edition? Is there any extra configuration needed. Hope can get some advice here, else I am unable to move on from database mirroring.
Many thanks and have a nice day.
Best Regards,
Harn