SQL Server Profiler returns incorrect hostname
We are using third party (Idera) software for auditing activity on our SQL Servers (2000) and some of the events collected do not contain correct data.
Idera SQL Compliance Manager uses Profiler to generate trace files which it then parses elsewhere. Idera suggests that the problem lies outside of their control as the incorrect data is being recorded by Profiler.
The problem is with hostnames. Some of our Excel and Access queries are old and were built on machines that no longer exist on our domain and the hostnames that Profiler pulls for events generated by the firing of these queries are the old ones, not the proper ones.
Why is profiler pulling these out-of-date hostnames?
What I need to do is somehow identify the culprit queries so that I can fix them and I really don't know how to best approach this problem.
Any suggestions would be greatly appreciated.
Software/Hardware used:
Software/Hardware used:
ASKED:
January 4, 2007 12:10 PM
UPDATED:
January 8, 2007 11:21 AM
Answer Wiki:
I would check any listed alias in the Client Network Utility. Also check for a hosts file located at c:winntsystem32driversetchosts. You can open this with notepad.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
