June 8, 2016 at 6:59 am
So I have a Windows 2012 R2 server with Windows Failover Clustering, and I set up a SQL 2014 Enterprise AlwaysOn AG with non-shared disk, and a non-standard port. Everything works fine, I am able to connect to the AlwaysOn Listener no problems and I don't need to put the port into SSMS and the failover works great.
So I am testing SQL 2016 under the exact same configuration, same Windows, SQL 2016 Enterprise Always On AG with non-shared disk, and a non-standard port. However, now SSMS requires me to put the port, and I can add the secondary node if I connect with the port, however, when I do the failover wizard since it automatically puts the name of the secondary server (without port) I can't launch a failover with the wizard. I'm afraid the Always On won't work properly with the non-standard port. I know 2016 is new, but does anyone have any ideas or thoughts on this? Our policy is to not use the standard SQL port for security reasons.
Update **
Okay so if I use the command ALTER AVAILABILITY GROUP [AOLNAME] FAILOVER; then the failover occurs. You just can't use the GUI, which will be a pain for the people that are on support that don't use SQL daily. The default instance should always connect without the use of port and this wouldn't be a problem.
June 14, 2016 at 6:56 am
Just a suggestion but give your support team a batch file that runs a SQLCMD command with your SQL?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply