Double posting is so rude... waste time answering one only to find answer on the other.

http://www.sqlservercentral.com/Forums/Topic430841-5-1.aspx

http://www.sqlservercentral.com/Forums/Topic430840-146-1.aspx

...and, if you're smart, you'll make the trigger code handle more than 1 row at a time. 😉

Two way street here, Jeff... how about posting your solution? Two reasons... like I said, "two way street" and the other is these types of problems typically lead to...

Double posting tends to tick folks off because they may spend some time of one of your posts trying to give you an answer only to find that a good...

Double post...

http://www.sqlservercentral.com/Forums/Topic430917-373-1.aspx

Look in the Index of Books Online for "cross-tab reports"... good example there.

Ok, Ray... I've changed the code above... minor tweak... should do what you want now... give 'er a try on a test table like the one you posted...

I don't think there's any overhead with CI... it's a difference of only 1 bit (32) and only an internal difference of what the mask looks like.

I love CI because...

p.s. Code above assumes all "Amounts" are negative... may have to make a second pass for positive "Amounts".

Yes... and for storing it, too. The following works on the data you provided for the tbExtract...

Yeah, I've seen that... but usually for smaller sets of rows.

Copy only the data you need for the report from the linked server into a local table... then, do the reporting off that and drop the table when you are...

Yes... you haven't DECLARED @db_name...

Then, try this...

http://www.sqlservercentral.com/articles/Advanced+Querying/anefficientsetbasedsolutionforislandsandgaps/1619/

Thank you, Jeff - from now on I will more-closely watch my use of inline queries.

Taking what Larry Taylor said a little bit further --

Jeff clearly states that...