Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » SQLServerCentral.com » Editorials » Does Connect Work?
Add to briefcase
18 posts, Page 2 of 2
««12

Does Connect Work? Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
Miles Neale
Posted Monday, March 04, 2013 12:05 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, May 20, 2013 9:51 AM
Points: 1,891, Visits: 936
I have not used it. Might in the future but will continue to use other avenues to get the information to MS when appropriate.

M.

Not all gray hairs are Dinosaurs!
Post #1426395
Revenant
Posted Monday, March 04, 2013 1:54 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 1:00 PM
Points: 3,459, Visits: 2,535
Gary Varga (3/4/2013)
. . . As a community we want better products and know that our collective opinions and knowledge count.

Microsoft has people who "own this line of communication." They need from time to time someone to let them know that their performance is under scrutiny.
Post #1426454
Peter Schott
Posted Monday, March 04, 2013 3:45 PM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Yesterday @ 11:01 AM
Points: 739, Visits: 927
I've largely given up on Connect. Sometimes I'll get a reminder about an item or a notification of something that could use some support, but too many I've submitted got a "Closed - will not fix" type response to make it worth my while submitting any sort of report. If I thought it was important enough to submit as a bug, then it should at least get some sort of pertinent comment indicating that someone actually looked at it and considered it.

I've also seen some things submitted that show up well after the fact as "fixed in the next version" which is just about equally useless if our company isn't upgrading to the next version so we can use whatever was fixed.

Sure it works sometimes, but on the whole I find it an exercise in futility to submit anything and just concentrate on finding a workaround instead.


Post #1426496
richardd
Posted Tuesday, March 05, 2013 7:54 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: 2 days ago @ 11:03 AM
Points: 1,854, Visits: 485
I'm still waiting for an explanation of why hundreds of perfectly valid bug reports were recently deleted. Even if they were closed as "won't fix", it was useful to know that the bug existed, and to see any possible workarounds.

I've lost count of the number of links to Connect bug reports I've clicked on in recent months which return "page not found" errors.

And I've seen too many valid bugs closed with comments to the effect that "we haven't got time to fix this now; we'll look at it later" which have then never been fixed.


Post #1426842
Gary Varga
Posted Tuesday, March 05, 2013 8:14 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:14 AM
Points: 3,540, Visits: 1,128
richardd (3/5/2013)
I'm still waiting for an explanation of why hundreds of perfectly valid bug reports were recently deleted. Even if they were closed as "won't fix", it was useful to know that the bug existed, and to see any possible workarounds.

I've lost count of the number of links to Connect bug reports I've clicked on in recent months which return "page not found" errors.

And I've seen too many valid bugs closed with comments to the effect that "we haven't got time to fix this now; we'll look at it later" which have then never been fixed.


Far from professional behaviour. Corporate responsibility Microsoft? Eh?

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1426855
Nadrek
Posted Wednesday, March 06, 2013 8:51 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, May 20, 2013 12:28 PM
Points: 675, Visits: 2,031
Revenant (3/4/2013)
Gary Varga (3/4/2013)
. . . As a community we want better products and know that our collective opinions and knowledge count.

Microsoft has people who "own this line of communication." They need from time to time someone to let them know that their performance is under scrutiny.


Please tell them that the cost of filling in all the fields required in a thorough manner is overwhelmingly too high to be worthwhile based on the expected response, which is for nothing to be done - this is overwhelmingly the most common response. The second most expected response is a note in the Connect article of "Will be fixed in next version", followed by it still being an issue in the next version. This is like the first response, except users have to wait quite awhile to see that.

It takes hours to do a thorough study of an issue, write up good explanations and precise instructions for how to repeat the results, as well as exploring for workarounds and writing up any found. For very interesting or intermittent issues, it takes much longer.

If it takes 4 hours to do that, and we expect less than 5% of Connect items to actually have something done about them, then we expect to spend in excess of 80 hours of effort per item actually addressed... with no idea which one of the items submitted will be addressed, if any.

Sorry; in all but the most critical cases, it's simply not worth the time.
Post #1427468
magasvs
Posted Wednesday, March 13, 2013 12:05 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, May 20, 2013 8:54 AM
Points: 1,259, Visits: 700
One of my favorite ones is: https://connect.microsoft.com/SQLServer/feedback/details/778203/books-on-line-has-bad-email-address-for-send-feedback
Pretty much the moral is: feedback does not work by design and it won't be fixed

It actually works for me, so it looks that Microsoft fixed it.
Post #1430556
Gary Varga
Posted Friday, March 15, 2013 6:26 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:14 AM
Points: 3,540, Visits: 1,128
magasvs (3/13/2013)
One of my favorite ones is: https://connect.microsoft.com/SQLServer/feedback/details/778203/books-on-line-has-bad-email-address-for-send-feedback
Pretty much the moral is: feedback does not work by design and it won't be fixed

It actually works for me, so it looks that Microsoft fixed it.


Unfortunately mail servers cannot send an automated response nor could they automate it to be processed by another system...hold on...erm...

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1431497
« Prev Topic | Next Topic »

Add to briefcase
18 posts, Page 2 of 2
««12

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.