Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running SQL Server 2000. While doing some profiling to trace activity, I noticed some hostnames showing up that were mysterious -- names that shouldn't exist on the network anymore. I got the MAC address for one of them from master.dbo.sysprocesses, looked up the IP address in the ARP cache, and then used nbtstat to resolve that IP to a network name. The name it resolved to was not the name in sysprocesses, nor was the name in sysprocesses resolvable on the network.

So where is this name coming from? Does SQL Server have a hostname cache somewhere that needs to be cleared? How can I fix this so that the correct network hostname shows in my traces?

share|improve this question
This is pretty common when dealing with Access and Excel connecting to the SQL Server, as the ComputerName which is passed in by default is the name of the machine which the file was first created on. – mrdenny Jun 22 '12 at 7:20
up vote 7 down vote accepted

This is set by the client.

It is passed in via the "Workstation ID" property in the connection string. So I presume that you will need to make some configuration updates on your client machines.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.