you can check out the posting here: Different Ways to Connect to SQL Server Instance
Here is summary of their findings:
1. Connecting using computer name
2. Connecting using system IP
3. Connecting using loopback IP 127.0.0.1
4. Connecting using localhost
5. Connecting using (local)
6. Connecting using just a dot (.)
7. Connecting using \\.\pipe\sql\query
8. Connecting using \\.\pipe\SQLLocal\MSSQLSERVER
9. Connecting using computer name with prefix np:
(to force to use named pipe protocol)
10. Connecting using \\.\pipe\SQLLocal\MSSQLSERVER with prefix np:
(to force to use named pipe protocol)
11. Connecting using (local) with prefix np:
(to force to use named pipe protocol)
12. Connecting using just a dot (.) with prefix np:
(to force to use named pipe protocol)
13. Connecting using \\.\pipe\sql\query with prefix np:
(to force to use named pipe protocol)
14. Connecting using localhost with prefix np:
(to force to use named pipe protocol)
15. Connecting using computer name with prefix tcp:
(to force to use TCP protocol)
16. Connecting using system IP with prefix tcp: (to force to use TCP protocol)
– Connect using TCP only without prefix also
17. Connecting using localhost with prefix tcp: (to force to use TCP protocol)
18. Connecting using (local) with prefix tcp: (to force to use TCP protocol)
19. Connecting using just a dot (.) with prefix tcp: (to force to use TCP protocol)
20. Connecting using loopback IP 127.0.0.1 with prefix tcp: (to force to use TCP protocol)
– Connect using TCP only without prefix also
21. Connecting using specifying port no.
No comments:
Post a Comment