There's also a "background" element to consider. I tend to see cursors crop up when it's language programmers (C#,VB,etc) trying to think in SQL. They tend to think imperatively because that's how they've been trained. However SQL tends to be functional in philosophy.

Perhaps a bit into the theory behind *why* cursors are bad would be helpful. The biggest hurdles I tend to run into are not the what to do instead of cursors, it's the breaking devs of the comfortable imperative practices. Once they understand they are trying to fit square pegs in round holes the discussions tend to go a little smoother.

So... an article like "Transformative Thinking", perhaps?