'SQL Server "." Alias Not Working
I've added an alias of "." which should point to my local (named) instance, ".\SQL2008". But when I try to connect to ".", it times out.
Am I missing something or is this not allowed?
Aliases I've tried which do not work:
(Set for both 32 and 64-bit, I've also tried leaving the port blank.)
Solution 1:[1]
If you are creating TCP/IP aliases you need to ensure the "SQL Server Browser" service is running. As well as checking the TCP/IP protocol is enabled for both server and client.
In Sql Server configuration Manager under the SQL Server Services node right click the SQL Server Browser and set the Start Mode to Automatic. If you are not going to do a reboot you will also need to Start the service manually.
The SQL Server Browser service is responsible for telling the client which port to use. See http://technet.microsoft.com/en-us/library/ms181087(v=sql.105).aspx for more details.
Solution 2:[2]
There is no limitation preventing that alias name. At leas it works on my machine ;)
However, when setting up the alias make sure you create it in the 32 as well as the 64 bit area:
I did also spell out localhost instead of just using the .:
Also, a SQL Server Alias always uses TCP/IP as connection protocol, which is not enabled by default. Under SQL Server Network Configuration (see above screen shot) check that TCP/IP is enabled for your instance.
Solution 3:[3]
It was not working for me after applied all the options mentioned here. For me, port number to TCP/IP protocol was not assign.
After assigning (highlighted in yellow color) it started working for me.
Solution 4:[4]
In your Alias definition remove the .\ from the Server box leaving just your instance name, that works on my machine. So in your case the dialog should look like this:
Solution 5:[5]
you need to run "cliconfg" and setup the alias on your local machine as well. If you have SSMS installed, create the alias in SQL Config Mgr, as this take precedance over the ones set in cliconfg. Remember, SSMS uses 32bit connection to SQL Server, even if is 64bit. If you don't set them locally, how does your PC know where to go for the alias. You could create DNS entries as an alternative.
Solution 6:[6]
I have a similar issue ,however on SQL server I did create alias on 32bit and 64 bit.I did the same thing on Sharepoint server using CliConfg. In short, for 64 bits Windows operating systems run: C:\windows\syswow64\cliconfg.exe For 32 bits Windows operating systems run: C:\windows\system32\cliconfg.exe on all server which you need to access to your database. Please see great article below. https://knowledge.zomers.eu/SharePoint/Pages/How-to-create-a-SQL-Alias-to-use-with-SharePoint.aspx
Solution 7:[7]
Also make sure the selected protocol for alias (e.g. TCP/IP) is enabled under SQL Server Network Configuration / Protocols for YOUR SERVER NAME
This was the issue in my case.
Solution 8:[8]
I followed everything on this page and it still didn't work only to try change the server my alias was set up against. I changed it to '.' as the server name, so it gets the machines local instance and then everything worked, don't know why it didn't like putting the name of the sql server instance but anyway!
Solution 9:[9]
I have a similar issue, In my case, I remove port No. and it works.
Solution 10:[10]
Mine worked after adding 32 bit Alias; run both 64 & 32 bit alias.
Solution 11:[11]
Despite my Client Protocol instances being set up on 64 bit SQL Native Client 11.0 Configuration, it wasn't until I set up Aliases in SQL Native Client 11.0 Configuration (32 bit), that the alias was recognized in Object Explorer. I didn't need to add the alias to SQL Native Client 11.0 Configuration at all.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow