Artificially increasing RowCount isn't the answer, especially if aspects in the code need to preallocate memory for resultsets, etc. In a sense this is why all queries contain the RowCount parameter - to not have unbounded requests (if I'm not mistaken there is also a safety cap override in the code). Once you've issued an infinite/unbound query to a database, closing the browser will not stop this from continuing to process.
If you are using something like an SQL stored procedure, then issuing SET ROWCOUNT 0 at the beginning of the procedure will allow sub selects and joins to not fall subject to the RowCount of the query, which like was mentioned, is there more appropriately for the returned resultset. Of course - this should be used with discretion.