Thank you a lot Noel, although this sounds complex, especially when the Reporting Software is involved. I guess I will need to transfer the SQLs first into a groovy script in order to isolate them.
Question though: is the any way to show running sessions with running queries and their applied actual execution plan? I would like to ensure first, that really the same plan is executed every time. Best regards Andreas On Saturday, November 23, 2019 at 11:26:31 PM UTC+7, Noel Grandin wrote: > > your best bet is to use either the H2 profiler, or something like VisualVM > to catch some stack traces to see where the code is spending it's time. > http://h2database.com/html/performance.html#built_in_profiler > > Post your trace here and somebody might be able to give you some ideas. > > Otherwise you will need to build us a standalone test case. > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/d3e466e3-679b-46a4-80c7-d95684f2ba24%40googlegroups.com.
