I beg to differ: I ran the DDL into DBVisualizer (references mode, circular view) and from the look of it this is a real database with obfuscated names.
Redesigning the database is not an option if it's not from the original author: the query itself has to be redesigned and this leads to the validity of the use case. @Itineric: can you share the application type and the use case of your query? On Thursday, December 8, 2016 at 9:22:46 AM UTC+1, Steve McLeod wrote: > > Your query is extreme. Hundreds of joins, dozens of nested selects. Way > too big, and way too complicated. You'll never get any decent performance > with a query like that, nor will you ever be able to analyse and understand > the reasons for the performance problems. > > The solution to your problem is to redesign your database. Read up on > database normalisation. > > If you need ad hoc, complicated queries, first load your data from your > normal schema into a star schema as described in database warehouse > textbooks. > > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
