Does anyone see a problem with copying a result set into a collection
for display vs looping through the result set for display, so I can
return the connection back to the database little faster? I am using
connection pooling, so there is no connection overhead in creating a
The only performance issue I can see that each result set will take up
memory, but after it's displayed, that memory will be available for
something else, right? I'm in a situation where up to 500 people can
hit a webpage for data at the same time.
I'm starting to run out of database connections on the web application
and a bigger database isn't an option for me. I can (and do) cache
persistant non-changing data, but have been told that calls for
changing and updated data must always come straight from the database.
Some of the result sets are over 10000 records long and there's no way
to split them. Through sql, I am able to return only rows X through
X+20, so I only return what I am going to show.
Any POSITIVE feedback would be appreciated.
Thanks in advance,