April 26, 2011 | SQL Server

A couple of fixes for Plan Explorer

This evening SQL Sentry has pushed out a new build of Plan Explorer 1.2 (build #6.1.32), fixing a couple of minor issues brought to our attention by users.

  1. Eric Humphrey (@lotsahelp) pointed out that our query timeout for generating an actual plan was set to 30 seconds. This was an oversight, but chances are you wouldn't see this in most cases:
    • if your query started returning rows right away, the timeout wouldn't occur, even if the query took longer than 30 seconds to complete;
    • if your query returned no rows (e.g. WAITFOR > 30 seconds), or took more than 30 seconds to start returning rows, the timeout would occur.
  2. Geoff Hiten (@SQLCraftsman) came across a plan that opened fine in Management Studio, but failed to open in Plan Explorer. This was certainly a first for us; usually, it is the other way around – SSMS frequently chokes on large or complicated plans that Plan Explorer opens with ease. In this case, the issue was caused by a self-referencing expression causing memory troubles in our new "Expressions" tab – which shows, among other expression details, a tree view of expression dependencies. So you can imagine what might happen with a circular reference – the code was prepared for a cap of 100 nested expansions per reference, but only if rendering them required less memory than what was available on the machine.

Both of these issues have been fixed and tested in the current download, which I recommend you apply to your system(s):

http://www.sqlsentry.net/plan-explorer/sql-server-query-view.asp

And the change list is published here:

http://downloads.sqlsentry.net/downloads/sqlsentryplanexplorer/PEChange_List.html

As always, please let me know if you have any questions about Plan Explorer, or come across any issues at all using the free tool.

 

13 comments on this post

    • AaronBertrand - April 27, 2011, 1:14 AM

      From Brooke Philpott (@Macromullet), our Senior Technical Lead:
      "The memory issue was exacerbated by the expression referencing itself multiple times, causing exponential growth. Not a common scenario."

    • TheSQLGuru - April 27, 2011, 3:34 PM

      2 minor requests:
      1) can you have the installer determine where plan explorer is currently installed and then default the install of the next patch to that location
      2) can you have the installer ask if/where a shortcut should be placed

    • SQLCraftsman - April 27, 2011, 4:51 PM

      Two words:  Vendor Code.

    • AaronBertrand - April 27, 2011, 5:55 PM

      Yeah, I understand, Geoff… some vendors can really make us learn new things about stretching SQL Server's boundaries. 🙂

    • Michael Codanti - April 27, 2011, 6:53 PM

      I would update if I could download it. (I'm curious to see if the bug I reported got fixed in this version.)
      I tried last night, and this morning, and I can't download either the change list or the application.

    • AaronBertrand - April 27, 2011, 7:00 PM

      Michael, can you be more specific – what do you mean by "can't download"?
      The links seem to be working fine for me. What is the actual symptom, and have you tried a different browser (in case some setting or add-in is blocking downloads)?

    • Michael Codanti - April 27, 2011, 7:38 PM

      It appears that downloads.sqlsentry.net isn't accessible from our corporate network. (I can get to it from home.) I have reported the problem to the HelpDesk, so hopefully they will get it resolved soon.

    • AaronBertrand - April 29, 2011, 9:29 PM

      Michael, if you send me your e-mail address, I will provide you with a more direct link that will bypass the CDN. Sorry about the inconvenience.
      Cheers,
      Aaron

    • Michael Codanti - April 29, 2011, 11:15 PM

      I got the new version and it appears to resolve my problem with some seek predicates not being shown as well. Amazing support for a free product, I wish I got as good of support for products we pay maintenance on. Thanks!

    • Brooke Philpott - April 29, 2011, 11:52 PM

      Thanks for the kind words and bug reports. We strive to make the product bug-free and we appreciate your taking the time to let us know about this. The particular issue you reported was ironically found internally while developing some new features for the next version. When you reported it I actually tried to repro with the main trunk and couldn't and then realized it was the same root issue (albeit a different manifestation). All I had to do was move it over and do a new build.

    • Seth Phelabaum - September 6, 2011, 4:49 PM

      Thanks for the explanation and notes of the timeout fix.  I was hitting this today and couldn't figure out what the heck was going on (as I'd run queries in the past that took far longer than 30 seconds to complete).  The actual change log is a bit misleading for this one:  3070 PA-Plan Explorer Actual plan collection will time out after 30 seconds.  That makes it sound like this was a change that was made intentionally, rather than the bug that was fixed.
      In any case, got the new version and all good to go.  

    • AaronBertrand - September 6, 2011, 4:56 PM

      Seth,
      It's not a feature, it's a defect. The name of the defect describes the symptom that has been fixed. Take a look at the other items under "FIXES" and you will see that the tone is the same, e.g. "Batches with identical statements can be sorted incorrectly" – surely we do not want to intentionally sort statements incorrectly?

    • Seth Phelabaum - September 6, 2011, 4:58 PM

      Heh, indeed.  I guess I should read more than a single line!

Comments are closed.