New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
alias support #71
Comments
This feature would attract a lot of DBA's who look after large multi-domain SQL estates, myself one of them. Ideally, and I will search for this after I write it, it would be nice to see compatibility with Central Management Servers and or at the very least - accept import of ".regsvr" registered servers files. |
I'd vote for being able to alias the connection name within SQL Ops Studio. Making the connection with the actual hostname is not a big problem as you'd only need to do that occasionally. However, once you have a list of servers, all of them with some long obscure name that's not easily identifiable, it becomes a problem. I'd like to see the option to add an alias (or name, etc) on the "Connection" screen when you add a connection. |
Connecting via an alias is not critical. Being able to alias them is a big deal, though. My org has hundreds of instances in production, with a very rigid (and very much worthless to me) naming convention. |
Started dealing with this issue yesterday. Can connect to a local named instance, but remote named instances that have aliases set up in SQL Configuration Manager locally won't connect. |
Hope this gets resolved soon. |
SQL Server Alias support is now available in Windows with the insiders and 1.40.1-rc1 builds, would request feedback from anyone waiting for this support. Unix support is not yet available as the feature works with Windows Registry at the moment. |
Gentle ping... This feature is now available in Azure Data Studio v1.40 on Windows, would appreciate any feedback! |
Thank you |
Closing this as now supported on Windows. |
Update distro branch with merge/1.62 updates
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: