ADO asynchronous queries and sorting
-
I have a stored procedure that executes too slowly (as I mention in a previous posting) so I'm thinking of executing the query asynchronously and grabbing the results as they come back. it may give the impression that the query is faster than it really is. my question is... the stored procedure is sorting the results. So if I grab the first few items from the recordset doing something simple like "MoveNext" and then the queries inserts items new items before the cursor because of sorting, I've missed those items. I am just beginning to dig into asynchronous querys so this may be a really stupid question, in fact I'm sure it is, but I've yet to see how to deal with sorting. Any suggestions?
-
I have a stored procedure that executes too slowly (as I mention in a previous posting) so I'm thinking of executing the query asynchronously and grabbing the results as they come back. it may give the impression that the query is faster than it really is. my question is... the stored procedure is sorting the results. So if I grab the first few items from the recordset doing something simple like "MoveNext" and then the queries inserts items new items before the cursor because of sorting, I've missed those items. I am just beginning to dig into asynchronous querys so this may be a really stupid question, in fact I'm sure it is, but I've yet to see how to deal with sorting. Any suggestions?
Once SQL starts the good ol' TDS stream, I'd presume that the records are correct (i.e. SQL won't return rows to you that aren't in the right order). Is it not possible to break up the stored proc. into smaller units? What kind of app is this for? Cheers, Simon "Sign up for a chance to be among the first to experience the wrath of the gods.", Microsoft's home page (24/06/2002)