Timeline for SQL Server 2019: Two Aliases point to same instance
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2021 at 16:58 | comment | added | Koughdur | The entries I showed you were from the SQL Server Configuration Manager Aliases. They were not from the hosts file. The examples on line have a backward slash and use localhost. I used to be a UNIX sysadmin and this confused me as to why it would work for the main instance, yet it did.. I did try a forward slash and that also gave me a "server not found" error. I tried a couple of things with the host file (using only valid characters) but nothing worked. Any ideas on what the alias should look like in SSCM? | |
| Jul 25, 2021 at 16:33 | comment | added | nbk | and yes in the sql configuration manager you can make a alias, but in sql server 2017 all changed a bit | |
| Jul 25, 2021 at 16:30 | comment | added | nbk | instances have [comuterma,e]/[server] that has nothing to do with aliases, which are configured in the hist file | |
| Jul 25, 2021 at 16:24 | comment | added | Koughdur | The naming convention for SQL Server instances is either [Computer Name] or [Computer Name]\[Instance Name]. All of the documentation on using aliases includes the "\" in the alias. If the hosts file can't have entries that include a slash, then the hosts file will not be a solution. Is there a solution using SQL Server Configuration Manager? | |
| Jul 25, 2021 at 16:19 | history | answered | nbk | CC BY-SA 4.0 |