Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?
I've been limiting the number of returned results in a table with two different approaches - either by using a calculation condition or using RANK/MAX in the expression. In terms of system resources and calculation time, which is worse? My assumption is that RANK/MAX would consume far more resources than a calculation condition, but I was wondering why that is. If my Calculation Condition is such that I require a certain minimum number of records before the expressions are run, isn't it just as taxing for the system to evaluate the entire dataset to make sure that condition is met?