How does SQL Pruning in the data model affects the report performance?
We have a customized version of the AP Aging report. The report performance is slow compared to the standard one.
To improve the performance we did some adjustment to the query, plus enabled the SQL Pruning in the data model properties.
While this successfully improved the performance of our report, we have a concern. In the lower environment, the runtimes are only around seconds to 1 minute. But in the live environment, it reaches around 7-8 minutes for the same parameters and exactly same data result.
Is it accurate to say that this is due to the SQL Pruning property? And is it normal for the runtime to be different between live and lower environment even if the data we are getting are the same? How can we make it the same performance as the lower environment?