SentryOne Team Blog (blogs.sentryone.com)

T-SQL Tuesday #86 : My Favorite Connect Items

T-SQL TuesdayThis month's T-SQL Tuesday topic is "SQL Server Bugs & Enhancement Requests." This is a topic near and dear to my heart; for several years I was a huge proponent of the Connect system. For a while, I even published weekly digests, where I highlighted bugs and feature requests that I thought deserved more eyeballs and votes. (A few people didn't like that – accusing me of giving preferential treatment and more visibility to issues I cared about. Yeah, that was kind of the point.)

I am still a firm believer in the improvement site, though I expend a lot less effort on it these days. Not because it doesn't work, but because the various teams have a less unified experience – some use various combinations of Trello, UserVoice, and Yammer, while only a few teams still seem to be using Connect.

For this month's T-SQL Tuesday, Brent Ozar (@BrentO) asked us to write about our favorite Connect bug or enhancement request. I'm going to do him one better, and talk about two different Connect items:

  1. My favorite unresolved Connect item
  2. My favorite resolved Connect item

I want to talk about both because, while I think it can be useful to promote important issues that haven't been addressed, I think it's also important to reinforce that Connect items do get considered by the team, and sometimes get fixed. There was certainly a period where it may have felt like all that work was going to /dev/null/, but I can assure you that's not the case today.

My favorite unresolved suggestion

There are so many active Connect items, it's difficult to choose just one, but after spending some time looking at the generate_series function in PostgreSQL, the one at the top of my list right now is this suggestion from Erland Sommarskog (blog):

0 replies on “T-SQL Tuesday #86 : My Favorite Connect Items”