Laurie beat me to it. Same as hers but no reason for the HiearchyLevel:
;WITH SearchHierarchy AS (
SELECT RegionID, RegionName, ParentRegionID
FROM [ParentRegionList]
WHERE RegionID = @Search
UNION ALL
SELECT a.RegionID, a.RegionName, a.ParentRegionID
FROM [ParentRegionList] a
INNER JOIN SearchHierarchy b ON a.ParentRegionID = b.RegionID
)
SELECT RegionID, RegionName
FROM SearchHierarchy
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