Getting Your &amp;amp;quot;Favorite&amp;amp;quot; SQL Server Bug Fixed

Microsoft Connect Resolution Reasons

Dan's Blog — Wed, 20 Aug 2008 17:22:28 GMT

In SQL Server we use Visual Studio Team System to track all of our work. There is a back-end integration

re: Getting Your "Favorite" SQL Server Bug Fixed

Chris Downey — Mon, 04 Feb 2008 23:35:08 GMT

<< One more last thing. I'm a big fan of Connect. Yes, it has its quirks, but it's an invaluable tool for collecting and responding to customer feedback. >>

Well... why is it so hard to Connect? Seems like it could be much easier, especially for the first time user who would like to report a bug. I've documented my first time frustrating experience with it here: http://web.mac.com/downeycp/CPD/Blog/Entries/2008/1/30_SQL_Server_2005_Invalid_Subquery_Bug.html

re: Getting Your "Favorite" SQL Server Bug Fixed

Dan Jones MSFT — Tue, 29 Jan 2008 20:28:50 GMT

Someone asked if there wa a tool they could use to generate the systrm information. You can use "System Information" and export the info to a text file. This provides far more data than we generally need, but it will save you a bunch of typing. The generated text file is ~800Kb.

re: Getting Your "Favorite" SQL Server Bug Fixed

Lizet — Thu, 17 Jan 2008 21:15:52 GMT

I understand there is no justification for using faulty language or offend the developers. Most of the users that report bug fixes are developers as well. I have reported a few bugs myself and have dealt with extensive hours on hold on the phone waiting for tech support. Once I get a hold of an engineer and he/she is able to test the repro, things go faster.

On the other hand, there has been several bugs, for instance in replication that did not happen on previous versions. SQL Server Developers should also understand that data loss is a serious problem for any organization, if the organization is a financial institution, the problem is even bigger.

There is a very annoying fact that bugs are not published or documented, I personally believe that if they are documented, even for only those users that have access to tech support, it would be easier to match an existing bug with the current problem, without waiting for a MS tech support to do the match.

We know everyone wants to have the bugs fixed, but it is worrisome that the numbers of bugs of a new version is higher to the previous version. Maybe slowing down the the new releases will ensure higher quality in the existing products?

Just my two cents...

Someone should be accountable for bugs that cause data loss/money to organizations, even if that someone is a very nice person.

re: Getting Your "Favorite" SQL Server Bug Fixed

anna — Mon, 14 Jan 2008 12:07:36 GMT

I'm sometimes amazed how personal people takes the bug issue. If you look at users you can sometimes think that the users think we have a complete bug list or that we have super powers to figure out what the problem are. And believing that a rotten attitude gets the problem fixed faster is so stupid.

But if you look at it from the other perspective, I often find developers taking pride in classifying something as a bug. In these days of agile and customer driven development, why taking so much pride into saying if something is a bug or a change request.

During the past two years we've gotten two synchronization bugs fixed in SQL Server 2005. My tips: be honest, give all information you have, understand that everyone wants to fix the bugs and don't forget that the guys fixing and confirming the stuff are people. Often really nice people. And also remember that reporting a bug is like going to the ER: sometimes there are people who are sicker than you and they need help first.

re: Getting Your "Favorite" SQL Server Bug Fixed

Tom Wickerath — Mon, 14 Jan 2008 05:21:43 GMT

Isn't there a tool (executable file) that one can run to fully document their system, dumping the output to a text file? I'm pretty sure there is, but I cannot remember the name of this tool right now. If you simply had folks run this tool and send the text file, it seems like the output should answer all questions raised in paragraphs 1 and 2.

Getting Your "Favorite" Bug Fixed

Tonys Microsoft Access Blog — Mon, 14 Jan 2008 03:54:12 GMT

A very interesting article describing how Microsoft personnel decides which bugs get fixed first. Getting

Meaning Of Names » Getting Your ‘Favorite’ SQL Server Bug Fixed

Meaning Of Names » Getting Your ‘Favorite’ SQL Server Bug Fixed — Sat, 12 Jan 2008 11:01:57 GMT

PingBack from http://meaningofnames.co.cc/getting-your-favorite-sql-server-bug-fixed/

Geek Lectures - Things geeks should know about » Blog Archive » Getting Your "Favorite" SQL Server Bug Fixed

Sat, 12 Jan 2008 10:07:02 GMT

PingBack from http://geeklectures.info/2008/01/11/getting-your-favorite-sql-server-bug-fixed/

Geek Lectures - Things geeks should know about » Blog Archive » Getting Your "Favorite" SQL Server Bug Fixed

Sat, 12 Jan 2008 10:06:55 GMT

PingBack from http://geeklectures.info/2008/01/11/getting-your-favorite-sql-server-bug-fixed/

Getting Your &amp;amp;amp;quot;Favorite&amp;amp;amp;quot; SQL Server Bug Fixed

Microsoft Connect Resolution Reasons

re: Getting Your "Favorite" SQL Server Bug Fixed

re: Getting Your "Favorite" SQL Server Bug Fixed

re: Getting Your "Favorite" SQL Server Bug Fixed

re: Getting Your "Favorite" SQL Server Bug Fixed

re: Getting Your "Favorite" SQL Server Bug Fixed

Getting Your "Favorite" Bug Fixed

Meaning Of Names » Getting Your ‘Favorite’ SQL Server Bug Fixed

Geek Lectures - Things geeks should know about » Blog Archive » Getting Your "Favorite" SQL Server Bug Fixed

Geek Lectures - Things geeks should know about » Blog Archive » Getting Your "Favorite" SQL Server Bug Fixed

Getting Your &amp;quot;Favorite&amp;quot; SQL Server Bug Fixed