June 6, 2008 | SQL Server

My biggest beef with RC0 so far

As Andrew Fryer pointed out earlier today on his blog, RC0 for SQL Server 2008 has been released to MSDN and TechNet subscribers.  What is RC0?  It may be the last public push we see before the product RTMs later this year.  It is feature complete, and from this point forward, only major show stoppers will likely be addressed before then.

I am writing to plead for your votes on a very important issue that came up for me using the new Activity Monitor, which is a show stopper for me.  There is a great new Activity Monitor which has a lot of new features, such as launching Profiler directly from a SPID list, and launching a showplan from a list of "Recent Expensive Queries."  This latter feature is completely broken for me, when connecting to a SQL Server 2005 instance.  I get an unhandled exception:

Unhandled Exception

I am hoping that you find this an important issue as I do… most notably because we will likely be upgrading our workstation client tools long before we upgrade all of the servers we manage.

So, I am asking for your votes in the following Connect item:

http://web.archive.org/web/*/https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=349494

4 comments on this post

    • Chris Wood - June 7, 2008, 1:03 AM

      Aaron,
      Connect seems to be full of RC0 install problems today. Does it install cleanly? I don't have access to MSDN to try it out.
      Chris

    • AaronBertrand - June 7, 2008, 5:07 AM

      It installed cleanly for me on two machines that didn't have a previous CTP.  I have a machine with CTP6 that I plan to try and upgrade on Monday…

    • TechVsLife - June 15, 2008, 10:00 PM

      My biggest beef is the failure to support the "installation" feature.  Unlike the ctps, the 32-bit version of RC0 will NOT install on any x64 OS: The new setup program is not designed to work on WOW64, or has a rule against running on WOW64, or something like that:
      http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3487869&SiteID=17

    • AaronBertrand - June 20, 2008, 4:58 AM

      TechVsLife, this issue has been reported on Connect here:
      http://web.archive.org/web/*/https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=351165
      You can add your vote and weigh in, and/or at least monitor the space for updates (maybe a workaround that will work for you has already been posted, or will be soon…).

Comments are closed.