I don't know how many folks here log into the Microsoft Connect site occasionally to check suggestions and bugs submitted to Microsoft for SQL Server and SSIS (still called DTS on their list). A small pecentage? Almost everyone? (Possibly in this group.) Anyone can vote for feedback they think is important. Theoretically issues with the most votes will get Microsoft's attention first.
Links to a couple new submissions that look interesting: 
1. SSMS/QA Style Message Logging for SSIS Execute SQL Tasks
2. ForEach SMO Enumerator Filtering
I vetted these issues in the forum first, so hopefully they're legitimate enough to warrant some useful feedback or even a few high fives!
Hi M.Glenn,
Those are important - thanks for pointing them out.
:{> Andy
|||Andy, thanks for the encouragement and votes. I wonder if it's common to enter a vote for your own suggestion? I'm inclined against it, but if everyone is legitimately entitled it might be helpful...
|||I generally don't. But that's just because I forget 
|||
Jamie, If that's the only reason in your opinion that's good enough for me. I'm heading for the voting booth! 
(Actually, now that I've given it a little more thought it makes sense since voting is the only way to tell Microsoft how important you think the suggestion or bug is.)
|||M.Glenn wrote:
Jamie, If that's the only reason in your opinion that's good enough for me. I'm heading for the voting booth!
(Actually, now that I've given it a little more thought it makes sense since voting is the only way to tell Microsoft how important you think the suggestion or bug is.)
I would tend to think that of the majority of bug submissions that the author deems it a high priority! ;)
Never-the-less, the voting system doesn't hold a whole lot of merit to it unless the voter gives his/her feedback to back up that vote. Microsoft has listened to plenty of my submissions without even having a single vote on them. And sometimes there are those with a large number of high votes that get closed (not fixed) because of one reason or another. So it all depends, in other words.
The moral is to be sure to leave appropriate feedback when voting so that you can leave your comments which may help clarify to Microsoft what exactly the bug is and how it impacts others.
|||Microsoft has listened to plenty of my submissions without even having a single vote on them. And sometimes there are those with a large number of high votes that get closed (not fixed) because of one reason or another. So it all depends, in other words.
The moral is to be sure to leave appropriate feedback when voting so that you can leave your comments which may help clarify to Microsoft what exactly the bug is and how it impacts others.
Good information. If that's the case, votes are not as critical as the site design seems to imply. The vote tally would probably be a bigger factor if the ratio of feedback submissions to Microsoft resources was high enough to overwhelm those resources. It sounds like they're able to review pretty much everything--another sign that SSIS is a high-priority product at Microsoft.
|||
I'm a firm believer that leaving a comment is much more valuable than a vote. If I were reviewing them then I would just ignore the votes cos of course most people are gonna vote high. I would want to know WHY this is important to you, how much grief has been caused without it? How could the product best be improved?
Qualititive feedback is much better than quantitive.
-Jamie
|||
I basically agree with what you guys are saying, but partly because Microsoft seems to be reviewing all submissions regardless of vote count. I would add that the vote itself is providing important qualitative information--showing at-a-glance how important the issue is for reviewers/commentators.
As for the original submitter, I could easily imagine voting a 3 or 4 on my own submission if it was cosmetic or less critical to me than other things I had in the queue. Human nature being what it is though, you guys are probably right about the temptation to give one's own submission a 5 in every case.
No comments:
Post a Comment