SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Performance issues with active/passive cluster - High tracewrite SQL times


Performance issues with active/passive cluster - High tracewrite SQL times

Author
Message
ian.todd
ian.todd
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 42
We run a vendor application in a clustered environment. When we fail over our SQL db our services come up and we're able to run smoothly, within a few hours we come to a complete standstill, this happens regardless of either node we fail over to.

One thing we are noticing is that there are initialization wait times that do not seem to be acting in a normal fashion. I ran the wait statistics query created by Paul Randal and we're noticing TraceWrite with extreme latency.

Has anyone ever experienced this type of issue before? We are running out of options. Any helps is appreciated.
Attachments
tracewrite.JPG (6 views, 55.00 KB)
Shawn Melton
Shawn Melton
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2337 Visits: 3513
This wait type is for SQL Server traces (Profiler, default trace, etc.) that someone may be running. You can disable the default trace if it is not needed but I generally do not see any issue with this trace running.

You may have someone else running a trace that is causing a high amount of overhead. You can view what traces are running on your instance by executing:

SELECT *
FROM sys.traces



As well if you find any other than the default trace I use this query to find out what events the trace(s) are capturing:

-- Gets all Events for a given trace id
SELECT a.[EventID], b.[name] AS [Even Name], a.[ColumnID]
,c.[name] AS [Column Name], d.[name] AS [Category]
FROM fn_trace_geteventinfo(1) AS a
INNER JOIN sys.trace_events AS b ON a.EventID = b.Trace_Event_ID
INNER JOIN sys.trace_columns AS c ON a.ColumnID = c.Trace_Column_ID
INNER JOIN sys.trace_categories AS d ON b.Category_ID = d.Category_ID
ORDER BY a.[EventID], a.[ColumnID]

-- This will return any filter conditions
SELECT a.[ColumnID], c.[name], a.[value], c.*
FROM fn_trace_getfilterinfo( 2 ) AS a
INNER JOIN sys.trace_columns AS c ON a.ColumnID = c.Trace_Column_ID
ORDER BY a.[ColumnID]



If you find any running that are capturing high overhead events [e.g. show plan] you can simply stop them with sp_trace_setstatus.

Shawn Melton
PS C:\>(Find-Me).TwitterURL
@wsmelton
PS C:\>(Find-Me).BlogURL
meltondba.wordpress.com
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search