No prob,

I'll focus briefly on the problems that cursors pose, and present 2 use cases for them---one being a CTE-based solution to the link provided in this post, and another for getting back identities after an insert/update. That's a fairly common use case---especially for DBAs that are maintaining older code with less of the newer features from 2008/2012.

This could easily turn into a series of articles, as avoiding cursors is directly tied to the topic of using set-based SQL vs. iterative SQL. There could easily be a dozen topics here, or more! Your call on how far you'd like this to go.

Thanks,

-Ed