We have about 10 or so users who have access to login to our database and run SQL Server Profiler.
The problem is that they're all using the same username/password to access the database, and every once in a while SQL Server Profiler causes everything to time out. So we're trying to track down who is running the profiler so we can see what exactly is causing the problem.
My developers are all over the country, so is there any way to see the IP address of who is running SQL Server Profiler on the database?
select c.session_id, c.client_net_address from sys.dm_exec_sessions s
inner join sys.dm_exec_connections c on s.session_id=c.session_id
where s.program_name like '%profiler%'
Of course the actual problem is;
quote:We have about 10 or so users who have access to login to our database and run SQL Server Profiler.
The problem is that they're all using the same username/password to access the database,
It's kinda like trying to track down the manufacturer of the bullets that were loaded in the guns of the gang that broke into your (unlocked and unalarmed) store and trashed the place. Developers should never be allowed to run Profiler, much less in production, and absolutely never using the same login (which I'm going to assume is sa).
Only if you run...wait for it...another trace. Or use a logon trigger or event notification to capture such information. You'd have to store that data in a table to maintain a historical record.
SQL Server Profiler issue
Posted - 04/26/2012 : 13:10:39
Or use a logon trigger or event notification to capture such information. You'd have to store that data in a table to maintain a historical record.