April 25, 2009 | SQL Server

It's Saturday, are you ready to vote?

I'm going to try to do this weekly; bring attention to some Connect items that I or colleagues nearby think are important but could use a nudge toward greater visibility.  This week I only have a few issues that I want to point out:

====================

More disclosure in sys.dm_exec_requests

Erland is asking for a column in the sys.dm_exec_requests DMV that shows when a statement started executing (currently it shows when the request started).  While you can get this information in other ways, it is much more cumbersome than being able to compare request time to execution start time.  I voted 5.

#435083 : Add column to dm_exec_requests that reports when the current statement started
http://web.archive.org/web/*/https://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=435083

====================

Giving us access to the "Connect to Server" MRU list

I wrote about this here a few weeks ago, but feel that a bit more exposure can't hurt (only 18 people have voted so far).  I think it's overkill that you have to destroy all of your preferences to remove one or two obsolete servers from the MRU list that populates the "Connect to Server" dropdowns within SSMS.

#424800 : SSMS : Expose "Connect to Server" MRU list to users
http://web.archive.org/web/*/https://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=424800

====================

Providing a real fix for the MSXML6 SP2 issue

Many people are still blocked by the fact that SQL Server 2005's installer is not smart enough to ignore the presence of MSXML6 when it tries to lay down those bits on an updated operating system (e.g. XP SP3).  While I don't use XP, and haven't suffered this issue personally, I have to agree that the workaround in KB #968749 is simply not sufficient.  At least for the SQL Server Express redistributable packages, the installer should be updated to simply skip MSXML6 if it is already there (in the current scenario the entire setup operation simply fails).  So I filed a suggestion for this:

#435245 : Update the SQL Server 2005 SP3 Express installers to bypass MSXML6 SP2
http://web.archive.org/web/*/https://connect.microsoft.com/SQL/feedback/ViewFeedback.aspx?FeedbackID=435245

====================

That's all I have for now.  Please vote on any issue that you deem worthy!

2 comments on this post

    • Alexander Kuznetsov - April 26, 2009, 3:44 AM

      Voted. The MSXML6 SP2 one is a shame – I saw it myself recently. Thank you for the digest, Aaron!

    • Terry Walker - June 17, 2009, 8:39 AM

      That's great, I thought about SQL Server like that before.

Comments are closed.