I am a bit curious how hunchback and my solutions would scale against a divide and conquer approach.
SELECT Shift
INTO #T
FROM @T
WHERE Rate = @Rate;
DECLARE @Rows INT = @@ROWCOUNT;
SELECT Rate
FROM @T
WHERE Shift IN (SELECT Shift FROM #T)
GROUP BY Rate
HAVING COUNT(*) = @Rows;
GO
DROP TABLE #T;
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