2017-01-10

T-SQL Tuesday #86: SQL Server Bugs & Enhancement Requests

For T-SQL Tuesday #86, Brent Ozar (b|t) asks us to "Find the most interesting bug or enhancement request..." (on Connect.Microsoft.com) ", and write a blog post about it."

If you've seen some of my recent posts, you know that Extended Events have been on my radar. So let's look at some Connect items for XEvents.

One Event Behind

I another post, I wrote that the XEvents event_stream target is regularly "one event behind". There is an existing Connect item seeking a fix to this problem: QueryableXEventData and “Watch Live Data” one event behind. If you use the "Watch Live Data" grid for XEvents in SSMS, this is an important issue and worthy of your upvote. It's also important if you ever want to access XEvent data programmatically with C# or PowerShell because the QueryableXEventData class uses the event_stream target and is also subject to the issue.


SQL Server Service Broker

.NET Framework programming isn't for everyone. Unfortunately, I don't know of any way to handle and respond to an XEvent using just T-SQL. Wouldn't it be nice if we could do that? Vladimir Moldovanenko certainly had similar thoughts. Check out his Connect item: Support SQL Broker Service to be a target of Extended Events. If we were granted our wish with this Connect item, we could handle XEvents via Event Notifications.

But wait! This item shows as "Resolved as Fixed". There are no details yet, though. Just a note that "This item has been fixed in the current or upcoming version of this product." I really hope this gets fixed for SQL 2016. Heck, I really want the fix back-ported to at least SQL 2012, to be honest. Please upvote this Connect item, and leave some comments asking for older versions to be fixed too. I'll be eternally grateful!


SHARE