August 24, 2011 at 2:42 pm
Can anybody give me the reasons why not to use cursors in detail...
Thanks..
August 26, 2011 at 8:41 am
I think the big issue is that a cursor is inefficient for many database operations. When we deal with relational databases the goal (or at least my goal) whever possible is to think in terms of sets. So those operations that can affect a set of records at a time versus a cursor where it works on a problem row-by-row. However not every problem can be solved this way which is why I think cursors are there.
This article had some pretty good insight on the benefits/consequences/pitfalls of cursors, how to work around them and how to work best with them if you have to.
Performance Tuning SQL Server Cursors
[/url]
Joie Andrew
"Since 1982"
August 26, 2011 at 9:10 am
Thanks for the link..
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply