>>HI
>>
>>In foxpro I would use Cursors for various purposes.
>>
>>IN SQL2005 I want to create a cursor or equivalent.
>>
>>What do others do about this.
>>
>>Should I just select my results into a table which I then drop when I've done with it or is that a bad thing to do.
>>
>>And if it is bad why ?
>>
>>(this is for a process that may be run weekly or possibly daily).
>>
>>Thanks
>>
>>Nick
>
>SQL Server is all about set-based operations. If you can perform your process with set-based, it will be better than using cursors.
>If there is absolutely no set-based alternative, then I suggest to read Brad Schulz series about cursors
>
>The Truth about Cursors - Part 1
>
>and other parts.

I'm not sure what you mean by set based operations

Thanks