Sean Lange (7/16/2013)
As Phil said, although more gently than me, you do not need a cursor for this at all. There is absolutely NO NEED for one. If you can explain why you think you need a cursor for some inserts we can quite easily demonstrate some alternatives that do not involve any kind of looping for this.
+1 to Sean and Phil.
Posted so the OP might gain inspiration from my mantra (below).
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