Incorrect HostName in SQL Server Enterprise Manager??

[Quanita]

Hi,
at the moment we are trying to isolate what processes are causing slowness on the server and have come across something strange, has anyone else seen this? is it due to an error in the setup or is this just a Enterprise Manager quirk?

Go into console root - SQL Server Groups - DatabaseName - Management - Current Activity - Process Info
in the host column (for example) there are lots of processes that are coming up as having my machine as the host, but these are users logged into the domain using other machines not mine - some of them may be connecting via a citrix connection. My machine is not a server.

We are using Microsoft Management Console 1.2
Version 5.0 Build 2195; Service Pack 4
SQL 2000

Any Advice would be appreciated
Thanks
Q

 

[Quanita]

I found this on another forum
*********************************************************
We created a new Access database on ComputerA that links to a table of the Northwind database on one of our SQL 2000 servers. When we open the Access database on ComputerA, the Process Info window shows ComputerA in the Host column. When we copy the Access database to ComputerB and open it there, it shows ComputerA in the Host column. When we unlink and relink the Northwind table on ComputerB, the Host column shows ComputerB. When we copy the modified database back to ComputerA and open it, the Host column shows ComputerB.

Basically, I've surmised that the client provides the net address and host information to SQL server and that, for some reason, when Access is the client, it provides the host name of the computer where the database was last modified
********************************************************

and have concluded that in addition to doing this for where the database was last modified it actually narrows it down to where the row in the database was last modified. That would explain why my machine and another developer's machine are most commonly listed as hosts. Our access db is used to run Crystal Reports which connect to the SQL Server.

 

[Catadmin]

Quanita,

Actually this happens a lot at our workplace. We use Access ADPs as a front end for our client and because the code is compiled on a specific developer's machine before each release, it always lists his machine in the SPWHO(2) and on Profiler as the HOSTNAME.

Unfortunately, there is no real way that I know of to change it so it accurately reflects the true PC name of the end user.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[mrdenny]

When you setup a connection string to SQL Server you can actually fake the hostname of the machine that you are connecting from by adding it to the connecting string. For some reason Microsoft Access does this when it connects to a SQL Server.

It's a known annoyance.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com