February 21, 2006 at 2:58 pm
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/mcAmri/sqlserver2005forsql2kdeveloperpart1.asp
March 29, 2006 at 7:14 am
Clean and clear demonstration of such a useful feature...
Thank you
March 29, 2006 at 8:12 am
I look forward to more...thanks!
March 29, 2006 at 8:41 am
Thanks for the examples. In case anyone is working through them, the case statement has a typo with a '2002' replaced with a '2001'
March 29, 2006 at 2:02 pm
Thankyou I found your article very helpful and presented in a clear style. I look forward to reading more of your work
March 29, 2006 at 10:31 pm
Hi Paul,
thanks for the correction of the typo.
The query still works fine, but order year 2001 will be interpreted as 2002 .
It should be like this:
SUM(CASE when OrderYear = 2002 then SubTotal ELSE 0 end) as '2002',
March 29, 2006 at 11:28 pm
i look farward for more. thanks !
slathar
March 31, 2006 at 2:52 am
Hi All,
I'm working on second installment of this series now. Just wait
May 11, 2006 at 2:53 pm
Good intro. Thanks.
I've got a question, though. Given this statement from your article:
INSERT INTO SalesByPerson
SELECT SalesPersonID, [2002],[2003],[2004] FROM Sales.SalesSummarry
PIVOT(SUM(SubTotal) FOR OrderYear IN
([2002],[2003],[2004])) as SalesPivot
is the IN (.....) required? What if I don't know the values and/or the values change? Am I stuck with dynamic SQL? Could I maybe put a sub-query (i.e. select DISTINCT OrderYear) in there?
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy