Exactly!

bhupendra.baraiya (4/16/2015)

---

we can achieve the same output without adding the rows Cluse

SELECT

CustomerID

, ...

samot-dwarf (4/20/2015)

---

I'm lazy and use FIRST_VALUE with ORDER BY x DESC instead of this extra long LAST-VALUE syntax.

Of course only if I don't need both (FIRST and LAST) because it...

amd.repetto (6/3/2016)

---

The only thing I must disagree is with the first statement "Windowing functions are the best thing since sliced bread when it comes to T-SQL".. they only will be...

EDIT: This is an answer to the question about using LAST_VALUE(TotalDue) OVER(PARTITION BY CustomerID, ORDER BY CustomerID)

There are a couple. First, the performance could be bad. ROWS will generally perform...

Nice solution!

Brian.Klinect (4/27/2015)

---

The explanation says why 3 is wrong, but why is 1 better than 2? The only difference I see is 1 has SUM(SUM(TotalDue)), while 2 has SUM(TotalDue) in...

I would say BOL does have an error. Not the first time. You can definitely use the OVER...

Be sure to reread the question and try all three queries in...

ROWS and RANGE are only supported with Window Aggregates (for example, running totals) and FIRST_VALUE and LAST_VALUE.

In your test, are you just performing the update or are you also selecting the data?

I'm not an expert on the Quirky Update, but don't you have to run the update which reads the entire table and then select the data after that which also...