THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

The Rambling DBA: Jonathan Kehayias

The random ramblings and rantings of frazzled SQL Server DBA

Updates to Extended Events Whitepaper

This is a place holder for updates regarding Extended Events for linking to in the whitepaper being published on MSDN. It will contain current problems, bugs, and connect feedbacks as well as known workarounds for existing issues.  As written in the whitepaper, it is recommended that you keep your installation of SQL Server up to date with the most recent Service Packs and Cumulative Updates as applicable to your specific needs.

As of the RTM version of SQL Server there were three bugs in Extended Events that affect the output of event data.  Of these, currently, only one has been fixed with a public release of the code fix, and the other two have possible work arounds available for them.

Bugs

 
 
Connect Feedback ID           N/A
Description Extended Events session produces an empty value for data captured for certain actions
Status Fixed
Hotfix Link 956717
Work Around Apply Service Pack 1 or CU1 to SQL Server 2008.
 
 
Connect Feedback ID 404168
Description Invalid XML in Extended Events xml_deadlock_report output
Status Fixed /Not Released
Hotfix Link
Work Around

The fix for this has been created, but it has not been publicly released.  There is a work around that has been published online in the following article on SQL Server Central.

http://www.sqlservercentral.com/articles/deadlocks/65658/

A simple replace operation can be used to substitute the invalid tags for correct ones as shown in the above article.

 
 
Connect Feedback ID 432548
Description Extended Events RingBuffer Partial Event Data when RingBuffer is Full
Status Active
Hotfix Link
Work Around The issue with this bug is that the serialization of the ring_buffer target data to XML for display in the DMV is limited to 2MB.  To get around this, use one of the file targets where event retention will exceed 2MB of data, or restrict the size of the ring_buffer to < 2MB of buffer memory.
 
 
Connect Feedback ID 433859
Description XE ring_buffer target does not show all collected events
Status Active
Hotfix Link
Work Around The issue with this bug is that the serialization of the ring_buffer target data to XML for display in the DMV is limited to 2MB.  To get around this, use one of the file targets where event retention will exceed 2MB of data, or restrict the size of the ring_buffer to < 2MB of buffer memory.
 
 
Connect Feedback ID 412484
Description Invalid Values in Bucketing Target Slots
Status Active
Hotfix Link
Work Around None Currently Available.

 

As new bugs and fixes are released, this page will be updated to reflect the newest information available.

Published Sunday, May 17, 2009 11:08 PM by Jonathan Kehayias

Comments

 

Roger C. said:

What whitepaper are you referrign to? Is there a link to it?

May 27, 2009 4:14 PM
 

Jonathan Kehayias said:

It is still pending publishing.  I had to put a permalink in the whitepaper which is why this post currently exists.  When the whitepaper is published, I will blog about it.  In the mean time if you have a question on Extended Events, you can feel free to contact me through the contact form on this blog, and I'll be happy to help by email.

May 27, 2009 4:21 PM
 

Jonathan Kehayias said:

Roger,

As luck would have it, the paper was published a few hours after posting my response to your comment.  I have posted information about the paper on the following post:

http://sqlblog.com/blogs/jonathan_kehayias/archive/2009/05/27/whitepaper-using-sql-server-2008-extended-events-published.aspx

May 27, 2009 8:30 PM
 

Roger C. said:

Great. Looking forward to reading the paper.

May 27, 2009 10:03 PM
 

jacobsebastian said:

Great work, Jonathan!

June 7, 2009 10:56 PM
Anonymous comments are disabled

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement