title: calculations in the report vs calculation in stored procedure
body: <p>I'm producing a report that has a calculation as one of the desired columns:</p>
  
  <pre><code>SELECT
     ....
     sum(SFLI.PLANNEDVOLUME) * PTS.KILOGRAMSPERUNIT as [WEIGHT],
  FROM
     ....
  GROUP BY
     ....
  </code></pre>
  
  <p>Another developer from my team, said that it would be better to move the calculation to the report rather than leave it in the stored procedure, because it is producing a bad execution plan. I did some research and it seems that moving calculations to the report can be bad for large datasets.</p>
  
  <p>So my question, is it super bad leave the calculation in the stored procedure? I'm pretty sure that SQL Server is smart enough to do things in parallel and even the execution plan won't be that bad. Am I wrong?</p>
  
  <p>PS: Without the grouping, we're talking about 250k rows, that grouped produces &lt; 250 rows.</p>