SSMS QueryPlan UI as a UserControl
-
vendredi 20 avril 2012 13:53
Hi Guys!
I am struggling with something, and don't know where to look... Maybe you can give me a hint?
I am trying to write a troubleshooting application for SQL, customized for our environment. One thing this app should do is help troubleshoot slow queries, and as part of this I would like to show the execution plan. Now... I do have the query plan in its XML format, that one is easy, what I am missing is a way to display this plan in a graphical format, like SSMS does. Is there any WPF Control or something like that to generate this?
thx
Lucifer
Toutes les réponses
-
dimanche 22 avril 2012 16:06Modérateur
Hello,
I am not sure that you are in the good forum .
A moderator can move your thread ( with your agreement in my case ) towards the Windows Presentation Foundation (WPF) Forum :
http://social.msdn.microsoft.com/Forums/en-US/wpf/threads
I would suggest to provide the XML format of your query plan to make easier for WPF specialists to help you .
Have a nice day
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.
- Marqué comme réponse Stephanie LvModerator lundi 23 avril 2012 05:59
-
dimanche 22 avril 2012 16:13
I am not sure if the WPF guys are the right ones for that question... Building a visualization for one specific plan XML is quite easy, but the SQL queryplans can vary in such a large quantity that building something from scratch seems hardly feasible (and not testible...) That's why I was hoping to find something within SMO that offers this possibility. In the end SSMS does it, and I always heard that everything SSMS can do is encapsulated in SMO somewhere...
-
dimanche 22 avril 2012 16:25Modérateur
Hello,
SOS already thrown for you.
"everything SSMS can do is encapsulated in SMO somewhere" : not exactly, as every statement in SMO is translated in T-SQL statement before being executed ( the T-SQL generated statements can be retrieved with the SqlCaptured class http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.common.capturedsql(SQL.100).aspx ). I think that it is the opposite ( and it is why SMO applications are slower than T-SQL statements, in execution time...)
Have a nice day
Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

