Extended Events - Histogram does not properly save existing_connection results - by mbourgon

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 785042 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/18/2013 10:33:46 AM
Access Restriction Public


For Extended Events, the Histogram is not properly saving the results from sqlserver.existing_connection.  Instead of saving out each unique value and a count, it returns one value and a count.    

I have tested this with both client_app_name and client_hostname - with client_app_name I always get "Microsoft SQL Server Management Studio - Query", with client_hostname I always get my machine name (when querying a different server)  

The histogram DOES work with other Events such as sqlserver.login.
Sign in to post a comment.
Posted by Stephen Mills on 10/16/2013 at 10:15 AM
Ouch. I've seen this a lot recently. When it isn't a huge bug, it gets closed and never fixed. I don't understand the reasoning behind it. If something is broken, it should be fixed. Why not set the status to postponed instead of won't fix. Also, why shouldn't users expect bugs in the current version to be fixed. But now they aren't fixed in the current version, but are never fixed and span into new versions as well. I think users will decide that if the money they spent doesn't justify fixing the bugs and they have to spend time and money to work around it, then maybe they should go to a cheaper solution (i.e. Open Source).

Can this be added to books online and documented that it is a known issue and the feature doesn't work?
Posted by Microsoft on 7/19/2013 at 5:20 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.