🚀 go-pugleaf

Are you with server-side cursor in ADO?

TDataset was designed to work with BDE and it slows down ADO. Also, ADO is
designed with Visual Basic and scripting languages in mind and this makes it
slower too - all fields are represented as Variants etc.

OLEDB Direct (http://www.oledbdirect.com) is faster then both ADO and BDE. 1
000 000 rows (3 integer columns) are inserted into SQL Server 2000 table on
PII-300 192 MB RAM in ~ 1 minute 20 seconds (database have file size and log
file size enough big to store this data) and fetchs them back in approx. the
same time. OLEDB Direct is more difficult to use then ADO but it is faster
and more powerfull. In this sample bulk-copy rowset is used (for insert)
that is not available from ADO. If you need source code for this sample,
write support@oledbdirect.com.

Regards,
Vassiliev V.V.
http://www.oledbdirect.com

"Roberto" <roberto@dialtech.com.br> �������/�������� � �������� ���������:
news:3d113a7d_2@dnews...
> Hi,
>
> I have tried to insert 100.000 recors in a SQL Server 2000 table and I
have
> abserved that BDE insertions are 6 times faster than ADO inserts on the
same
> environment.
>
> My question is: How could this be possible ???
>
> Note: Searches are 4 times faster in BDE too.
>
>
>
>
>
>