Re: DAO & ADO performance
ADO uses whatever OLEDB provider you specify.
There is a native OLEDB provider for Jet databases, but there is also an OLEDB provider for ODBC data sources.
I can easily imagine that ADO is slower the DAO as far as jet databases are concerned. This is not true for SQL Server, though.
Re: DAO & ADO performance
I tried same application on SQLServer also.But not so much difference.
How is the performance of OLEDB 2.0 Interface.
Ksheeraj
39639,Leslie St.
Apt #157
Fremont USA 94538
Re: DAO & ADO performance
for accessing SQLServer I use the OLEDB provider for ODBC data sources exclusively. I have done some minĂ*mal testing with the native OLEDB provider for SQLServer, but IMHO it sucks!
"Many things" simple don't work with that provider and I didn't want to waste time finding out why.
As for performance: well it has to be a bit slower than ODBC, because the OLEDB provider for ODBC uses ODBC as the underlying interface.
I have not found any performance issues in my applications so far.
Re: DAO & ADO performance
Hi,
I've experienced some performance problems with ADO. First of all, I suggest you run Profile to see which task is most time consuming. If you find that it is INSERT, then maybe you're opening a recordset to the table, a task which is very time consuming. Instead, try using the Connection.Execute() method.
Hope this helps.
Bye,
Axe.