I got completely distracted by this article's use of "Dynamic SQL". Dynamic SQL is a fairly specific concept on our platform, and historically there's been a small difference between Dynamic and Embedded SQL in terms of overhead, but that has all but evaporated over the past few years by consecutive optimizations. Now suddenly this article seems to suggest there's a huge gap, so I got hooked and dug into the code, only to find that this method is making a rather crazy detour through %DynamicObject for no real reason, on the way from the SQL result set to the dataframe. In other words, all you're measuring between the "Dynamic SQL" and "IRIS SQL" options is exactly that %DynamicObject overhead.

It's only a name, true, but people only doing a cursory read of the article may take away the completely wrong thing.

For those excited about Table Partitioning, my colleague @Ben Schlanger just posted an updated set of kits and some extensions of the tutorial, including support for MOVE PARTITION with nonempty partitions, and how to use the ALTER TABLE t CONVERT .. command to turn a non-partitioned table into a partitioned one. All of this is on track to be included with IRIS 2026.1 in the new year!

We don't want you to get bored during the holidays ;-)

Still a test case would be helpful.

If there's no source table rows for which userActionten=1, that value will not show up as a dimension member in Analyzer (so no row in the pivot with COUNT equal to zero). Maybe that's what you're seeing?