Probably obvious from the tone of my question, but even though I prefer upper-case keywords, I don't feel it is our job as editors or reviewers to encourage and even reward behavior that is merely the enforcing of one's preferences onto others. I understand that often the intent is to improve the post. But on its own I don't think this should be a valid ...


For me the best option would be #3 - save the file as .sqlplan and post it somewhere that does not require a login to download. You want to make obtaining the file easy, not hard, for people trying to help you. Saving as a .sqlplan makes it easy for us to open it in Management Studio, Plan Explorer, etc. The problems with the other methods: A picture in ...


My answer is a firm NO. There's only a handful of reasons that I can think of that would make it ok to edit someone else's code in either a question or answer: there's a typo that would prevent the code from working as is. reformatting to lay out the code so that it's visible. no nitpicking, just taking bunched up 1-2 lines of code and spreading it out ...


I don't think such upper-casing editing is a good idea, because it might discourage people from some cultures. AFAIK, some languages do not have the concept of uppercase/lowercase at all. People from such cultures might not value upper-casing the way we do. They may use upper and lower cases interchangeably, and IMO they should not be discouraged from ...


For SQL Server, you can also upload the XML execution plan to PasteThePlan.com Simply paste the XML form of the execution plan into the box, hit Submit, then share the link in your question or answer.


If you try to upload a longish PostgreSQL query plan, the best option is explain.depesz.com, I think. It provides a quite intuitive interface with which you can easily discover the critical parts.


SQL SERVER generates the SQL PLANS as XML documents, so what you are looking at on your screen is actually an XML document parsed by SQL Server and put into that graphical component. Given the parser is not available outside, you cannot by any means create a JPEG out of this. There is simply NO PICTURE created here, just an XML file. You could either save ...


Please use Code Review, a Stack Exchange site dedicated specifically to, well, code review.


dbfiddle.uk does a great job of displaying execution plans for SQL Server, Oracle, and Postgres. The default page (for each respective RDBMS) lists instructions which should be pretty self explanatory. It even handles the graphical XML output quite well for SQL which I wasn't expecting at all.

Only top voted, non community-wiki answers of a minimum length are eligible