SELECT

km_ndc

,CASE WHEN SUM(extended_amount_corrected)

+ SUM(qty_corrected)

...

Not really a better way to write that, but you could replace the AND's with + and test to see the performance difference.

SELECT

km_ndc

,CASE...

My rulle of thumb is regardless of what "everyone says" is best to run both ways and compare the results. Then you'll know for sure. 😀

OK, that just blows the pants off mine. :hehe:

Something like this should mix up your numbers ... you may have to run it a couple of times to verify that you get all records.

WITH startingList

AS (SELECT

...

User RETURN

ALTER PROCEDURE [Video].[addVideo]

@Title nvarchar(50),

@uri nvarchar(200) ...

Not Arith Abort, but Numeric Round-Abort

You have "Numeric Round-Abort" set to True on the 3054 DB. Change it to false and it will run without a hitch.

That would explain it. It's because you add in another element to the Pivot without aggregating it. You'll need to remove that column from the results or comma delimeted list...

LOL, I've been called worse.

Read up on NULL in BOL ...

Select Count (Distinct ConsultantID) from @t

Where DeactivationDate = '2007-09-04'

And ISNULL(StatusID, '') <> '72HOURRESIGNATION'

Really? IT works on my Adventure works DB just fine.

Are you using the EXACT code I posted?

I hate to be the bearor of bad news Andras, but your query produces a cartesean product. :ermm: Your query returns some 3000 rows, and mine is the original 64....

You essentially need to run the pivot two seperate times and join on the product name. This may not be the most efficient way of solving your problem, but this...

Hey, who the heck is this Joel guy? :hehe: