March 13, 2018 at 3:43 pm
Hi
Is there a way we can find if someone ran SQL profiler 2 days back?
March 13, 2018 at 7:00 pm
gary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
Not likely.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2018 at 4:07 am
Short of asking people, no.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 14, 2018 at 5:30 am
gary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
Hmmm! you don't know if the profiler was run nor who might have possibly done so? Somehow I thing you have a bigger problem on your hands.
π
May I ask what is the reason for this, were there performance problems?
March 14, 2018 at 7:38 am
gary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
If you still have default traces from that time, it would be in there.
Event class would be Audit Server Alter Trace Event. You'd look for exec sp_trace_create in the text data. Application name would be SQL Server Profiler - xxxxxxx
Sue
March 14, 2018 at 1:29 pm
Eirikur Eiriksson - Wednesday, March 14, 2018 5:30 AMgary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
Hmmm! you don't know if the profiler was run nor who might have possibly done so? Somehow I thing you have a bigger problem on your hands.
π
May I ask what is the reason for this, were there performance problems?
True that!
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
March 14, 2018 at 1:30 pm
gary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
How many people have sufficient rights to run profiler? This gives a pretty granular (perhaps in the wrong hands dangerous look) at your environment.
<hr noshade size=1 width=250 color=#BBC8E5> Regards,Jeffery Williams http://www.linkedin.com/in/jwilliamsoh
March 14, 2018 at 3:16 pm
Gary1,
Traces started by Profiler are recorded in the errorlog. sp_readerrorlog 0, 1, βtraceβ.
March 15, 2018 at 6:00 am
gary1 - Tuesday, March 13, 2018 3:43 PMHiIs there a way we can find if someone ran SQL profiler 2 days back?
the sql error log will record a trace start and trace stop event with the trace id and the user id who initiated it
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" π
March 15, 2018 at 7:40 am
Perry Whittle - Thursday, March 15, 2018 6:00 AMthe sql error log will record a trace start and trace stop event with the trace id and the user id who initiated it
Enterprise DBA - Wednesday, March 14, 2018 3:16 PMGary1,Traces started by Profiler are recorded in the errorlog. sp_readerrorlog 0, 1, ‘trace’.
Thank you both for that. Learned something new.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply