Satheesh Bandaram wrote: > Rick Hillegas wrote: > > >>For all of our diagnostic output, there's probably a big payoff in >>moving to some more structured format like xml. That will help >>client-side (and even off-the-shelf) tools format the output and >>filter out unwanted information. > > > I agree... Current diagnostic tools could be improved. Generating in XML > does help processing and visualizing the info. DB2, for example, has a > good way to display query plans and costs and I think this can be saved > in XML format. Current output of DumpOptimizedTree is huge and hard to > follow for even mid sized query. > > But since I have immediate need for optimizer trace output , I was > suggesting enabling it in current form before attempting to make it > better. Also would give us a chance to use and understand what it is > before making it better.
If you have an immediate need for it and it's a developers' tool then it's already available, hack the code to enable it. Creating a property to enable it instantly makes it a feature of the product, this is open source, the code is open, users can see the functionality available. And if there is a property to enable it then it's just a matter of time before someone asks a customer of theirs to run it at their site to diagnose a customer's problem. Dan.
