You might try this:
SELECT CompanyName, Type
,Sunday=MAX(CASE WHEN weekday = 1 THEN Val END)
,Monday=MAX(CASE WHEN weekday = 2 THEN Val END)
,Tuesday=MAX(CASE WHEN weekday = 3 THEN Val END)
,Wednesday=MAX(CASE WHEN weekday = 4 THEN Val END)
,Thursday=MAX(CASE WHEN weekday = 5 THEN Val END)
,Friday=MAX(CASE WHEN weekday = 6 THEN Val END)
,Saturday=MAX(CASE WHEN weekday = 7 THEN Val END)
FROM dbo.TestGrid
CROSS APPLY (
VALUES(High, 'High', DATEPART(dw, CAST(DateID AS CHAR(8))))
,(Low, 'Low', DATEPART(dw, CAST(DateID AS CHAR(8))))) a(Val, Type, weekday)
GROUP BY CompanyName, Type
And you will also want to Google "SQL DATEFIRST" to see how this query is sensitive to that setting.
You can look at the first link in my signature to see how the CROSS APPLY VALUES works (like an UNPIVOT but usually faster).
I won't ask (but should) why (before someone else does) you're storing a date as an INT instead of a DATETIME.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St