You're welcome!
Now I have to look up "arduous" in my dictionary...
Thanks Peter. It is very good procedure and I shall use it.
R. M. Joseph
You are welcome!
I am satisfied you liked the article. I really struggled to keep it simple and consise. And as you write, my purpose was to give away the base of what pivot tables really are.
Fantastic Article,
I now need to somehow work out to add ordering based on these "unknown" columns but this is a great start to stuff I really did not understand.
A Huge help - thanks.
The article was re-released today, so don't take it personal
About PIVOT and UNPIVOT in SQL Server 2005; I have more use for UNPIVOT than PIVOT...
You could update the table creation to get the datatype of temporary table directly from the source instead of the hard-coded types/sizes. This would be easily done with:
SELECT RowText, ColumnText, Value FROM Source WHERE 1=0 INTO #Aggregates
Which works because the 1=0 clause insures no rows are matched, but the datatypes are set according to the soruce...
1) Why would I? Then you have no control over the datatype for the aggregated column VALUE (sum).2) The syntax is wrong. It should be SELECT .. INTO...FROM ... WHERE ...
Thanks for the post.
Very simple,perfect.Would like to see similar post from you
