InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 10:23:33 GMT20http://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxThanks for pointing out the missing spaces in the script. The edit tool didn't preserve the original spaces so I added them back. The revision is awaiting appoval.Sat, 22 Oct 2011 13:56:31 GMTDan Guzman-481633http://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxHi Dan,First, thanks for the article, it's been very helpful.I saw your earlier reply regarding the versioning, and I should have been clearer. I was referring to the missing spaces in the FROM section, which should be corrected to:[code="sql"] FROM sys.traces AS t CROSS APPLY FN_TRACE_GETEVENTINFO(t.id) AS tdef JOIN sys.trace_events AS tevent ON tdef.eventid = tevent.trace_event_id JOIN sys.trace_categories AS tcat ON tcat.category_id = tevent.category_id JOIN sys.trace_columns AS tcolumn ON tcolumn.trace_column_id = tdef.columnid[/code]It's simple to correct, but the original doesn't parse in SSMS as is.Thanks for the quick response,MikeSat, 22 Oct 2011 08:28:41 GMTgrokmannhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxI corrected the script in the article shortly after Sammesel brought this to my attention. As I mentioned in my other response, the other issue is that the script is intended for databases in 90 and later compatibility mode.Thanks,DanFri, 21 Oct 2011 18:41:33 GMTDan Guzman-481633http://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxsammesel is right, but this code should be corrected in the article. Please and thank you. :-PFri, 21 Oct 2011 11:23:32 GMTgrokmannhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxHah! You're absolutely correct! The DB is indeed running in (80) compatibility mode :pinch:Thanks for the quick response...Thu, 04 Aug 2011 07:32:35 GMTphatdogpromoshttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxThe Server-side Tracing stairway is targeted at SQL 2005 and later versions. Since the error message refers to the CROSS APPLY line, I suspect you are either running this on a SQL 2000 server or from a user database in SQL Server 2000 compatibility mode (80). Thu, 04 Aug 2011 07:02:06 GMTDan Guzman-481633http://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspx[quote][b]sammesel (2/23/2011)[/b][hr]Great article, looking forward for next step.I had a little problem when running the query - but it was easy to spot where the problem was. [code="sql"] SELECT t.id AS TraceId , path AS TraceFilePath , tcat.name AS EventCategory , tevent.name AS EventClassName , tcolumn.name AS ColumnName FROM sys.traces AS t CROSS APPLY fn_trace_geteventinfo(t.id) AS tdef JOIN sys.trace_events AS tevent ON tdef.eventid = tevent.trace_event_id JOIN sys.trace_categories AS tcat ON tcat.category_id = tevent.category_id JOIN sys.trace_columns AS tcolumn ON tcolumn.trace_column_id = tdef.columnid WHERE t.is_default = 1 --default trace AND t.status= 1 --running ORDER BY TraceFilePath , EventCategory , EventClassName , ColumnName ;[/code]thanks[/quote]Even using this modified code my server will still not parse?Msg 102, Level 15, State 1, Line 8Incorrect syntax near '.'.Seems to be failing at the parameter (t.id) ?Microsoft SQL Server 2005 - 9.00.3080.00 (X64) Sep 6 2009 09:15:46 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)Thu, 04 Aug 2011 02:19:35 GMTphatdogpromoshttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxGood article... Looking forward to read the next part of the series...Thu, 24 Feb 2011 00:06:44 GMTAnipaulhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxRony, I'll cover the sp_trace* procs in detail in the next Stairway level, How to Create a SQL Trace Using T-SQL.With client-side traces, a SQL Trace rowset provider runs on the server to handle returning trace results to the client application. If the client doesn't consume trace data as fast as it is generated, the trace buffers fill on the server and server threads sending event data will wait for free buffers. Consequently, a slow trace consumer can slow down queries and overall server performance. The rowset provider waits up to 20 seconds before dropping trace events.Wed, 23 Feb 2011 20:31:21 GMTDan Guzman-481633http://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxLooking forward to the rest of this series, thanks!Wed, 23 Feb 2011 15:19:02 GMTUMG Developerhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxGood article. Interested to read the next step. I expect you will include those sp_trace* procedures as well.A quick question on this, if the server side operation is to just dump the events collected into the client side application like profiler, then how would the server be affected in performance ? Won't that be an issue only at the client side (comparing the client side & server side traces)? Thanks,RonyWed, 23 Feb 2011 11:04:40 GMTrony.ajhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxA good start to an overview to SQL trace.It'd be useful if the next one detailed the difference between profiler and server side tracing where one uses rowset and the other file provider (guaranteed to be loss less).Wed, 23 Feb 2011 08:50:02 GMTMysteryJimbohttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxGreat article, looking forward for next step.I had a little problem when running the query - but it was easy to spot where the problem was. [code="sql"] SELECT t.id AS TraceId , path AS TraceFilePath , tcat.name AS EventCategory , tevent.name AS EventClassName , tcolumn.name AS ColumnName FROM sys.traces AS t CROSS APPLY fn_trace_geteventinfo(t.id) AS tdef JOIN sys.trace_events AS tevent ON tdef.eventid = tevent.trace_event_id JOIN sys.trace_categories AS tcat ON tcat.category_id = tevent.category_id JOIN sys.trace_columns AS tcolumn ON tcolumn.trace_column_id = tdef.columnid WHERE t.is_default = 1 --default trace AND t.status= 1 --running ORDER BY TraceFilePath , EventCategory , EventClassName , ColumnName ;[/code]thanksWed, 23 Feb 2011 08:34:34 GMTsammeselhttp://www.sqlservercentral.com/Forums/Topic1063673-2903-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/SQL+Trace/71693/">Stairway to Server-side Tracing - Step 1 - Overview of Tracing (Stairway Series)</A>[/B]Mon, 14 Feb 2011 10:37:05 GMTDan Guzman-481633