Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
 Posted - 2012-03-20 : 22:25:25
|
| One of our server has only a named instance—no default instance. However, users are able to connect the default instance. Under the hood, users are in fact connecting to the named instance. My conclusion: somewhere there is a name resolution happening. Some process, converts SERVERNAME TO SERVERNAME\INSTANCE_NAME. There are no entries in sys.servers for this mapping. Also, there are no ALIAS entries in the network configuration utility. Has anyone seen this behavior?------------------------I think, therefore I am - Rene Descartes |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2012-03-20 : 23:59:57
|
| There is No alias on the client machine. I am doing this on the server itself, by loging remotely. I am pretty sure that the server is using the default port? Would, using the default port, cause this behavior?------------------------I think, therefore I am - Rene Descartes |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-03-21 : 05:09:05
|
| Yes, all that named instances are are SQL services listening on non-default ports.Now a named instance would not be listening on the default port (1433) by default, someone would have to have set that up--Gail ShawSQL Server MVP |
|
|
|
|
|
|
A question on Named Instances.