Excuse me for butting in here, on a job that you seem to indicate is complete.
I strongly advise you reconsider how you're constructing the @SQL string. Wherever you've concatenated in a local variable, you should instead be referring to a dynamic sql parameter which you can then assign when you use:
EXEC sp_executesql @SQL, N'@yr=@yr', @yr=1946
This avoids possible issues with SQL injection.
BOL has some good examples here: http://technet.microsoft.com/en-us/library/ms188001.aspx
I also show how to do this in a recent article published by SSC:
How to Design, Build and Test a Dynamic Search Stored Procedure [/url]
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