How about something like this?
;WITH PriorQueryResults AS (
SELECT Table_Name='Project Phase', [Lookup Table Value]= 'Build'
UNION ALL SELECT 'Project Phase','Closure'
UNION ALL SELECT 'Project Phase','Implementation'
UNION ALL SELECT 'Project Phase','Initiate'
UNION ALL SELECT 'Project Phase','Plan'
UNION ALL SELECT 'Project Phase','Transition'
UNION ALL SELECT 'Project Status','Cancelled'
UNION ALL SELECT 'Project Status','Complete'
UNION ALL SELECT 'Project Status','In Progress'
UNION ALL SELECT 'Project Status','Logged'
UNION ALL SELECT 'Project Status','On Hold'
),
AddRowNum AS (
SELECT Table_Name, [Lookup Table Value]
,n=ROW_NUMBER() OVER (PARTITION BY Table_Name ORDER BY [Lookup Table Value])
FROM PriorQueryResults
)
SELECT [Project Phase]=MAX(CASE Table_Name WHEN 'Project Phase' THEN [Lookup Table Value] ELSE '' END)
,[Project Status]=MAX(CASE Table_Name WHEN 'Project Status' THEN [Lookup Table Value] ELSE '' END)
FROM AddRowNum
GROUP BY n
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