I am using ADO in ASP to exec a fairly substantial stored proc in Oracle. The procedure is called in the db via an ADODB.Command object, which is using ADODB.Parameters. I am finding that calls to Command.Execute, which I am using to return a recordset, are coming back extremely quickly.
However as soon as I test for RecordSet.EOF, a massive delay is incurred (over 100 sec). Is this because the call to the database is carried on asyncronously until the data is actually needed, at which point the EOF test becomes a blocking call that takes ages to execute? Or does my recordset exist as soon as Command.Execute has finished, but due perhaps to poor db tuning, the EOF call is adding unnecessary time to the whole process?
Let me know if this is insufficient info to go on. Thanks all in advance