Cursors. Satan's operand.
I hate them. There is nothing more annoying that working through someone's crap code which is failing, to find you need to decrypt their perverted thinking just to work out what is going on.
Apart from the fact that cursors are slow, I have never (I said 'NEVER') seen a case where cursors are necessary. In every case I've ever come across, there has been a better way of doing things. If you need to process data row by row, you can do this better and faster using a while loop, a select statement and a couple of marker variables.
If your reading this and you think I'm wrong, then you need to do a bit more research on set theory and then you may (I hope) come to understand why cursors are such terrible operations for a relational database.
I suspect cursors were invented to allow old COBOL programmers to be able to work with databases.
If I was offered a job where I never had to deal with cursors, and badly written code in general, I would gladly take a pay cut (well, just a small one) !