I realize transpose / crosstab are not in the In-DB tools, but could you use SQL to handle your pivot / un-pivot and modify the data to allow for the use of the Summarize-In-DB tool and then process the MIN() vertically instead of horizontally? Most database engines do better with tall, skinny data tables rather than wide.
But regarding your example, there shouldn't be a reason for this length of processing. I'm guessing you have a memory leak somewhere or the database isn't allowing for the processing of that many fields against the function for however many rows of data you have...
Sorry I couldn't be more direct in answering, but wanted to get some alternative thoughts going for you. -Jay
User | Count |
---|---|
108 | |
82 | |
69 | |
54 | |
40 |