January 23, 2013 at 6:42 pm
If I open the default trace log in sql server profiler to view.
It opens all the rollover files in one window.
Is there a way that I can filter out the records by some criteria?
I don't see an option, I can see a find... option, but it is not very helpful.
January 23, 2013 at 7:34 pm
What version of Profiler are you using? I get a popup asking me if I want to open the next Rollover file.
I'm using Profiler from SQL 2008 R2.
Leo
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
January 23, 2013 at 7:40 pm
In SQL 2005 & 2008, Under SQL Profiler Options there should be a radio button under "File Rollover Options" to say "Prompt before loading rollover files". And yes, there is also a way to filter and search through the trace file itself - click on the "find" icon, or press Ctrl-F
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 23, 2013 at 11:36 pm
Much easier to use fn_trace_gettable and then filter within SQL. The profiler GUI's a pain to filter, sort and search in.
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
January 24, 2013 at 12:09 am
In addition to what Gail said, here is a simple script to Read from the default trace
DECLARE @path NVARCHAR(260);
SELECT @path = REVERSE(SUBSTRING(REVERSE([path]),
CHARINDEX('\', REVERSE([path])), 260)) + N'log.trc'
FROM sys.traces WHERE is_default = 1;
SELECT *
FROM ::fn_trace_gettable(@path,DEFAULT)
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 24, 2013 at 9:32 am
Thanks all.
Yes that's what I found too, I am using 2008, and it prompts if I want to open rollover files. And I see a Find button that is not very helpful to search.
I think I will use T_SQL then.
Thanks
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply