Jeff Urlwin wrote:
FYI, its the same for both SQL Server and Sybase. The TDS protocol that communicates with the server (which both use) causes the limitation.Using the latest DBI and DBD::ODBC to connect to SQL Server I'm getting this error...Connection is busy with results for another hstmt (SQL-S1000)(DBD: st_execute/SQLExecute err=-1) This happens when I use the same database handle to execute two different statements. When I open two different connections, this problem does not exist. It must be some sort of a DBD::ODBC or ODBC config, since using OLEDB, this also is not an issue.Yes, this is a known issue and one caused by the driver itself. Sybase also seems to have (or used to have) this limitation.
Any "workaround" operates by causing TDS to only return one row per fetch, by default; after the select the entire result set is pushed down the wire, so its not possible to have two concurrent result sets.
Nick.
