<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body>
I have heard of a faster way especially for Bulk ADDs or DELETE's, with
about a 5 to 1 increase in speed in certain cases, using ODBC API driver
calls directly and turning SQL_AUTOCOMMIT off. using :<br>
Declare Function SQLSetConnectOption Lib "odbc32.dll" (ByVal hDbc As Long,<br>
ByVal fOption As Integer, ByVal vParam As Long) As Integer<br>
<br>
I don't know how stable this is but was used in days of yore with Access
2.0 and I believe some C++ programmers still use.<br>
<br>
Susan Harkins wrote:<br>
<blockquote type="cite"
cite="mid006001c2f7c3$c55c2930$dae6ffcc@SusanOne">
<pre wrap="">I'm not really concerned about bloat at this point -- I'm just interested in
opinions about which performs faster: DAO or SQL.
Susan H.
</pre>
<blockquote type="cite">
<pre wrap="">Speaking MDB's, and SQL as in SQL code, then you're tapping the JET engine
in all 3 cases be it by query or 2 diffrent forms of code. When access an
MDB via code, DAO is always faster, but ADO is more suitable if you will
also be tapping into other data stores such as SQL Server or Oracle. In
reguards to database bloat, an MDB will bloat because of the required
database space to store a temporary file be it sql or code.
IF you mean SQL as in SQL Server, then the advantages are many, but one
</pre>
</blockquote>
<pre wrap=""><!---->that
</pre>
<blockquote type="cite">
<pre wrap="">comes to mind is the tempdb which is very useful because it holds all the
data temorarily when using groupby's or order by's in your SQL code, of
course you can't access this via DAO unless of course you have the table
linked to a MDB.
-Francisco
<a class="moz-txt-link-freetext" href="http://rcm.netfirms.com">http://rcm.netfirms.com</a>
On Monday, March 31, 2003 9:26 AM [GMT-8],
Susan Harkins <a class="moz-txt-link-rfc2396E" href="mailto:harkins@iglou.com"><harkins@iglou.com></a> wrote:
: Charlotte and I are having a brief discussion off list of how SQL can
: solve some bloat problems. Now, I find SQL superior to DAO/ADO almost
: everytime and would rather work in SQL if given the choice. However,
: I have seen discussions about performance right here on this list --
: do any of you think DAO/ADO performs faster than SQL? If so, can you
: provide some statistics?
:
: SUsan H.
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>