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.