Arne Vajhøj wrote:
AlexS wrote:
>"Mark Rae" <ma**@markNOSPAMrae.netwrote in message
news:eb**************@TK2MSFTNGP03.phx.gbl...
>>"Troy Bull" <tr*******@gmail.comwrote in message
news:uk**************@TK2MSFTNGP04.phx.gbl...
My number 1 preferred solution would be to have my program just use
an ODBC datasource
ODBC is *extremely* old technology by now.
A native .NET data provider will run rings round ODBC in terms of
performance...
any hard data on performance gains/losses?
It would be easy to test.
So I did.
:-)
A completely randomly picked test gives:
SQL Client (2.0): INSERT 20000 rows: 9,109375 seconds
SQL Client (2.0): 50 SELECT 20000 rows: 1,75 seconds
OLE DB (2000): INSERT 20000 rows: 20 seconds
OLE DB (2000): 50 SELECT 20000 rows: 62,140625 seconds
ODBC (2000): INSERT 20000 rows: 16,65625 seconds
ODBC (2000): 50 SELECT 20000 rows: 47,8125 seconds
OLE DB (2005): INSERT 20000 rows: 17,28125 seconds
OLE DB (2005): 50 SELECT 20000 rows: 61,484375 seconds
ODBC (2005): INSERT 20000 rows: 13,96875 seconds
ODBC (2005): 50 SELECT 20000 rows: 47,734375 seconds
I can post the code if anyone wants to see it.
Arne