@sean, Cursors were never on bad performance, its upto you when and how you use them. Some developers use them very early rather than creating complex set based queries, some use them only as a last resort.

In some tightly couple systems (or rather I would say badly designed) there are cases where you cannot change existing code and objects and have to end up using cursors or some iterative approach to get things done.

Here @rocky_498 is also trying to solve a business problem by using this approach, because calling an SP for different set of values is not possible by a set based approach. Even if he tries to do so, he has to deal with 8-pages log Stored Procedure which his manager won;t let him touch, or it would become itself a big project.

In a nutshell I would suggest you to go through all responses and give them a thought wrt your scenario. And as we don't know how complex is your existing SP, so try to use CURSOR approach, check this link for using cursors optimally: http://sqlwithmanoj.wordpress.com/2011/02/07/avoid-cursors-or-use-them-optimally/[/url]