Cursors remind me of the Army. Give a Private a shovel and tell him to fill in the huge hole one shovel full at a time, when there is a good bulldozer sitteing right there that could do it in one pass.
I spent many an hour removing cursors from legacy code. It was the biggest culprit in processing time and resources. A lot of this code came from developers who wrote SQL for ETL, but it wasn't limited to developers.
It is a good topic as noted previously that has been covered many times. It has been my experience that once a person gets the hang of writing SQL statements instead of cursors, the person usually abhors the use of cursors also.
Well here's your shovel have fun...;)
Q
Please take a number. Now serving emergency 1,203,894