I tried to define an alias on a server (as part of a database consolidation), but it doesn't seem to work. These are the steps I did:
Started SQLcmd.exe from a client as "sqlcmd -Snwgalias -E", but it's returning "could not open a connection to SQL server" Server is 64bit and so is client, so I created a 2nd alias (NWGALIAS2) under the "SQL Native Client 10.0 configuration" (I assume the is 64bit), but with no result.
What am I doing wrong?
Create the alias on the client
answered May 21 '12 at 06:19 PM
Is TCP an enabled protocol for the instance?
Is the SQL Server Browser service running for the server?
.. .. ..
Now, this is local, would there be a need for DNS to have an entry that points client PCs to my IP address so they can get picked up by SQL Browser service and passed(via the alias) to my instance?
As per the MSDN / SQL Server documentation on Creating Server Aliases:
And the rest of that introductory paragraph makes it pretty clear that these are for client machines, rather than server-side setup, and this is confirmed by the structure on the left of the page, where it shows the following:
etc, showing that this is part of the Client network configuration.
answered May 22 '12 at 08:32 AM
SQL Server Configuration Manager is not a tool which is installed on a client. So I assume you run this on a server.
Running cliconfg.exe on a client and creating an alias works, but that's not an option for me. This alias trick was mentioned as a temporary solution, until we manually changed the connection definition on each laptop to the 'real' servername.
answered May 22 '12 at 08:50 AM
Wilfred van Dijk