I have a create table query which creates a table with records (multiset), and a secondary query that inserts records into it (millions of rows from the first, hundreds of thousands from the second). The explain seems to indicate better performance when doing this vs running the same queries using set table with aggregates (results in half the rows), but it is difficult to actually test for each since during the week there is a high volume of use on the system & queries can take sometimes an hour to run, but on weekend volume is so low the queries run in seconds. Multiset results in no aggregate operations, but a whole lot more rows to insert...set with aggregate requires more resources to aggregate but results in much fewer rows. From a technical standpoint, which would be more efficient?
Forums: