Is there performance penalty for returning resultsets instead

Thanks Dan for these numbers. In the mean time I performed some tests of
my own. To my surprise, I found out that main problem is not with
cursors and result sets, but with SELECT COUNT(*)!
For 50k rows and when page is at the beginning of table COUNT takes
about 10x more time than fetching 30 full rows!
I need that count, to display exact number of pages to user.
Since I'm making admin utility I also thought to show row count for each
table in a database but I'm not sure about that now.
DejanThanks Dan,
I'll probably use sysindexes for final solution. @.@.CURSOR_ROWS won't
work for me as I'm using DYNAMIC cursor, which always returns -1.
Dejan