We habve set up SQL Server 2012 Always on between 2 (I1 and I2) computers using the listener as a connection point.
I1 is primary (Read Write)
I2 is sub (Read Only)
If we connect via the Listener we get hooked to I1 (verifed using @@SERVERNAME)and all sql executed changes flow as expected to I2
However when we do a failover (automatic or manual) so that I2 becomes primary and I1 is now sub the listener still connects to I1 as the base (using SSMS to verify) and tries to send all commands to I1. Which then fail as I1 has become readonly as the sub.
Reconnecting seems to have no effect.
Is this expected behaviour for the Listener ? or should it have directed the connection to the new primary I2 ?
Do we have to drop all connections for the Listener to repoint to the new primary I2 ?
Is this a configuration issue on my end ?