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 |
|
delpiero
Yak Posting Veteran
98 Posts |
 Posted - 2006-06-28 : 11:21:16
|
| Hi all, Recently I set up SQL Server activity audit trace by using stored procedures like sp_trace_create, sp_trace_setevent, etc. Everything looks good and we have our trace files available. However, I found that in the HostName and ApplicationName fields of the trace output, entries only exist for those connections from Enterprise Manager or Query Analyzer/isql, etc, but not for those applications which connect through ODBC. For these ODBC connections, we are able to get everything (stored procedure command line, login account, etc.) but just except the HostName and ApplicationName fields, which are shown blank. Has anyone come across with this problem? We wish to audit also the hostname and application name of these connections.Thanks,Del Piero |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-28 : 12:16:53
|
| Those values are only available if the client populates them. Sounds like you have applications that don't set them.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
delpiero
Yak Posting Veteran
98 Posts |
Posted - 2006-06-28 : 18:27:41
|
| nr, how can the client application populate these values for SQL Server Profiler? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-28 : 18:39:50
|
quote:
Originally posted by delpiero
nr, how can the client application populate these values for SQL Server Profiler?
It is done in your application's connection string.Tara Kizeraka tduggan |
|
|
|
delpiero
Yak Posting Veteran
98 Posts |
Posted - 2006-06-29 : 06:39:25
|
| tkizer, did you mean it is related to the ODBC connection parameters? If it is, which parameter affects the profiler trace behaviour? I am using Microsoft SQL Server ODBC Driver Version 03.85.1117. Thanks,Del Piero |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-29 : 11:30:36
|
| I can't help you with the specifics of fixing this since you are using ODBC. You'll have to check the documention for your ODBC driver to see where to set these.Tara Kizeraka tduggan |
|
|
|
delpiero
Yak Posting Veteran
98 Posts |
Posted - 2006-07-05 : 00:46:32
|
| Thanks. I guess I have to set the "APP" and "WSID" parameters in the ODBC connection string. Del Piero |
|
|
|
|
|
|
|
|
Problem with SQL Server Profiler Trace