Anyone come across one stored procedure, using a couple of cursors who in turn uses a few sp's that rely on several udf's so you end up with this huge tree? Where instead some temporary tables with the correct queries would just shorten it down to a very very small tree instead? I hate cursors that is used regularly in the code when in my mind cursors should only be used for easy use for something you want to do once. I find people who write cursors are not used to sql but keep the c/c#/java/etc programming style with them into the database.