SSMS - SQL Server Management Studio 2012 missing connection properties for availability groups - by DanMcClain

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 786323 Comments
Status Closed Workarounds
Type Suggestion Repros 8
Opened 5/3/2013 1:41:33 PM
Access Restriction Public


SQL server 2012 SSMS connection properties for Always on in a multi subnet failover is NOT retained by SSMS. Nore are they availalbe to set during a SQL server registration. Is extremely time consuming to manually enter parameters every time.

Example: MultiSubnetFailover=True;ApplicationIntent=ReadOnly
Sign in to post a comment.
Posted by DBAUser2015 on 4/17/2015 at 6:54 AM
I agree with AG_. We are doing a POC testing for SQL 2014 and it is frustrating to see that the below workaround does not work for ApplicationIntent=ReadOnly for redirecting to a secondary node through a AG listener. I don't think it even recognizes the ApplicationIntent property in the string. Appreciate if someone can please take a look at this.
Posted by aG_ on 3/23/2015 at 3:54 AM
Nope, bummer. The workaround mentioned here does not work, at least not for ApplicationIntent=ReadOnly for redirecting to a secondary node through a AG listener. And yes, I have specified a database that is a part of that availability group. It does connect to that database but on the primary node instead of secondary.
Posted by Charles [MSFT] on 3/10/2015 at 4:17 PM
Thank you everyone for your reports. This issue has been fixed and will be included in the next major release of SSMS.

In the meantime the following steps provide a workaround :

1. Open SSMS
2. Browse to the "Registered Servers" view (View -> Registered Servers)
3. Right click on "Local Server Groups" and select "New Server Registration"
4. Fill out the dialog with the appropriate connection information for your server
5. Click "Save"
6. Exit out of SSMS
7. Browse to %APPDATA%\Microsoft\Microsoft SQL Server\$(Ver)\Tools\Shell (where $(Ver) is the SQL version such as 110, 120, 130 of your SSMS install)
8. Open RegSrvr.xml in a text editor
9. Find the <RegisteredServers:Name> node with the name of the server you just created
10. Edit the <RegisteredServers:ConnectionStringWithEncryptedPassword> node and add any other parameters you want to the end (such as MultiSubnetFailover=true)
11. Save the file
12. Start SSMS
13. Browse to the Registered Servers view again
14. Double click on the node in the tree for the server you created to connect Object Explorer to that server

Please note that if you make any later modifications to the registered server through the UI any custom parameters you've added will be overwritten. Also this does not work if the registered server information is stored on a CMS (Central Management Server), it will only work for locally stored servers.

-Charles Gagnon (
Posted by Brandon.Tucker on 10/6/2014 at 12:07 PM
Still present in 2014 RTM SSMS. One thought would be for any connection from SSMS to, by default, include the MultiSubnetFailover=true property (since it doesn't hurt in non-multi subnet setups).
Posted by Mobious1 on 4/15/2014 at 12:08 AM
Are there any workarounds or patches likely as this is such an annoying oversight and I cannot believe that it still exists in 2014 after being raised over a year ago? Please fix this as it's driving me crazy!
Posted by Roadkill on 4/1/2014 at 3:19 PM
Still an issue in SQL 2014 SSMS.
Posted by johnaau on 2/27/2014 at 4:08 PM
This is also an issue in SQL Management Studio 2013 and is very annoying.
Posted by Microsoft on 5/8/2013 at 7:10 AM
Hello Dan. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (