Discussion concerning the free SQL Sentry Plan Explorer
1/8/2012 7:48:20 AM
alexf01
Posts: 2
|
Hi,
First of all, the plan explorer is really great! Thanks for creating such a wonderful (and free) product.
I'm often using sp_whoisactive's @get_plans feature -- this gets the plan of running queries as an xml column.
Clicking this xml opens the execution plan graphically in a new tab.
When I use right click -> view with sql sentry plan explorer, the program opens, but I get the error:
There was an error loading the file:
Could not find file 'C:\Users\alexfr\Documents\ExecutionPlan1.sqlplan'.
Showing the xml and copy-pasting it into the plan explorer works fine.
Please help!
Thanks,
Alex
|
|
0
• permalink
|
1/8/2012 10:15:28 AM
Aaron Bertrand
Moderator
Posts: 57
|
Hi Alex,
Could you share a little more information?
(1) when you observe this symptom, do you have one instance of Management Studio open, or multiple?
(2) what version of Plan Explorer are you using (Help|About) and when did you install the Management Studio add-in?
Thanks,
Aaron
--
Aaron Bertrand, Senior Consultant
SQL Sentry, Inc.
|
|
0
• permalink
|
1/8/2012 10:44:11 AM
alexf01
Posts: 2
|
Hi Aaron,
Well, that solved it -- I needed to update the add-in (the plan explorer was already up-to-date).
Looking inside the installer file, mine had its content created on July 27th, while the latest one is August 4th (is there a version number somewhere?).
Thanks!
Alex
|
|
0
• permalink
|
1/8/2012 10:50:25 AM
Aaron Bertrand
Moderator
Posts: 57
|
Hi Alex, the first release of the add-in had an issue surrounding file handles passed from Management Studio. We released a fix rather quickly. The reason the add-in is separate from Plan Explorer is that the logic involved is quite simple, and we know that it will change at a much slower rate than Plan Explorer. Since the add-in requires an SSMS restart, we felt it best to keep it as its own separate, simple file so that changes to Plan Explorer do not force you to restart SSMS just so that we can replace the add-in component with an identical copy.
We'll look into how to improve that in the future. But to be quite honest, we don't anticipate many changes to the add-in at all, unless they significantly change the add-in infrastructure beyond SQL Server 2012. I'm sorry this caused a pain point for you but at the same time I'm glad I was able to help resolve your issue quickly.
Cheers,
Aaron
--
Aaron Bertrand, Senior Consultant
SQL Sentry, Inc.
|
|
+1
• permalink
|