N
Nick
We try to migrate our ASP appliations to ASP.NET and
expereance some strange performance drops when replacing
ADO ODBC recordset queries by ADO.NET DataReader Objects.
Especialy reading a single row from a large table (>
4.000.000 data rows) by selecting the row using the
primary key. It is 50 to 100 times faster in ADO ODBC than
in managed ADO.NET (Same Query statement, same SQL
Server...). It seems to be a BUG in the implementation of
the SQLDataAdapter in .net.
Any hints and work arounds / (or BUG fixes) apreciated.
expereance some strange performance drops when replacing
ADO ODBC recordset queries by ADO.NET DataReader Objects.
Especialy reading a single row from a large table (>
4.000.000 data rows) by selecting the row using the
primary key. It is 50 to 100 times faster in ADO ODBC than
in managed ADO.NET (Same Query statement, same SQL
Server...). It seems to be a BUG in the implementation of
the SQLDataAdapter in .net.
Any hints and work arounds / (or BUG fixes) apreciated.