In the code below, it appears that I have a different result whenever I change the order of the element above the denominator. Since these are just simple addition and subtraction operators why would it make a difference how they are ordered. I was finally able to get it woking properly but I am a bit confused about the operatior order of precedence.

(SELECT DV.ForecastYear, @Metric1, ( Sum(case when MetricName=@Metric1 then MetricValue end) + Sum(case when MetricName=@Metric3 then MetricValue end) + Sum(case when MetricName=@Metric4 then MetricValue end) - Sum(case when MetricName=@Metric2 then MetricValue end) + Sum(case when MetricName=@Metric5 then MetricValue end) - Sum(case when MetricName=@Metric6 then MetricValue end) ) / Sum(case when MetricName=@Metric7 then MetricValue end) CalcResults, @spid FROM Metrics M2 INNER JOIN DataVersion DV ON M2.DataVersionRowID = DV.DataVersionRowID WHERE DV.DataVersionID = @DVID AND MetricName in (@Metric1, @Metric2, @Metric3, @Metric4, @Metric5, @Metric6, @Metric7) Group by DV.ForecastYear)

Are you sure you have no other changes except the order?
There should be no difference whatsoever however you order these lines:

Sum(case when MetricName=@Metric1 then MetricValue end)
+ Sum(case when MetricName=@Metric3 then MetricValue end)
+ Sum(case when MetricName=@Metric4 then MetricValue end)
- Sum(case when MetricName=@Metric2 then MetricValue end)
+ Sum(case when MetricName=@Metric5 then MetricValue end)
- Sum(case when MetricName=@Metric6 then MetricValue end)

Just a thought, if @Metric1 through 6 are always DISTINCT, this should simplify it

Sum(case when MetricName in (@Metric1,@Metric3,@Metric4,@Metric5) then MetricValue end)
- Sum(case when MetricName in (@Metric2,@Metric6) then MetricValue end)

But re your question, the order should not have mattered as all if that is your full query.

0

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.

I suggest you to do the aggregations first and then apply the calculations.

SELECT ForecastYear, Metric1, (sum_1 + sum_2 + sum_3 - sum_4 + sum_5 - sum_6) / sum_7, spid FROM ( SELECT DV.ForecastYear, @Metric1 Metric1, SUM(CASE WHEN MetricName = @Metric1 THEN MetricValue END) sum_1, SUM(CASE WHEN MetricName = @Metric3 THEN MetricValue END) sum_2, SUM(CASE WHEN MetricName = @Metric4 THEN MetricValue END) sum_3, SUM(CASE WHEN MetricName = @Metric2 THEN MetricValue END) sum_4, SUM(CASE WHEN MetricName = @Metric5 THEN MetricValue END) sum_5, SUM(CASE WHEN MetricName = @Metric6 THEN MetricValue END) sum_6, SUM(CASE WHEN MetricName = @Metric7 THEN MetricValue END) sum_7, @spid spid FROM Metrics M2 INNER JOIN DataVersion DV ON M2.DataVersionRowID = DV.DataVersionRowID WHERE DV.DataVersionID = @DVID AND MetricName IN (@Metric1,@Metric2,@Metric3,@Metric4, @Metric5,@Metric6,@Metric7) GROUP BY DV.ForecastYear) t1

It really shouldnt matter. With divides, you need to be careful of using integers rather than decimals, so sometimes do a * 1.0 to ensure it uses decimal arithmatic.

The only thing I can think of off the top of my head is maybe NULL values upsetting the aggregate functions.

Using your original, and by the way both cyberkiwi and sharath have good suggestions above...

( Sum(case when MetricName=@Metric1 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric3 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric4 then MetricValue else 0.0 end)
- Sum(case when MetricName=@Metric2 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric5 then MetricValue else 0.0 end)
- Sum(case when MetricName=@Metric6 then MetricValue else 0.0 end)
)

-- should be the same as

( Sum(case when MetricName=@Metric1 then MetricValue else 0.0 end)
- Sum(case when MetricName=@Metric2 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric3 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric4 then MetricValue else 0.0 end)
+ Sum(case when MetricName=@Metric5 then MetricValue else 0.0 end)
- Sum(case when MetricName=@Metric6 then MetricValue else 0.0 end)
)

also your denominator should also be checked, not just for "else 0" but also that it is in fact not zero.

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

After restoring a Microsoft SQL Server database (.bak) from backup or attaching .mdf file, you may run into "Error '15023' User or role already exists in the current database" when you use the "User Mapping" SQL Management Studio functionality to al…

Occasionally there is a need to clean table columns, especially if you have inherited legacy data. There are obviously many ways to accomplish that, including elaborate UPDATE queries with anywhere from one to numerous REPLACE functions (even within…

If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you!
In this Micro Tutorial, you'll learn yo…

Add bar graphs to Access queries using Unicode block characters. Graphs appear on every record in the color you want. Give life to numbers.
Hopes this gives you ideas on visualizing your data in new ways ~
Create a calculated field in a query:
…