Here's an interesting programming question; there are three dimensions
here, so bear with me.
I have one particular view in SQL Server that takes two tables (one
consisting of about 15 records and the other a few hundred thousand
records), inner join them, count the records, and group by one field.
It seems, under Enterprise Manager, that this query is quite
intensive, since it usually times out.
As a test, I went into MS Access 2000, created a new database,
connected to the SQL server via ODBC, linked the two tables, and
created the same query. The results are generally returned in under a
I've been writing an interface with Visual Basic 6, using the SQL
Server OLE DB provider (through ADO). (I'm under the impression that
Enterprise Manager also uses OLE DB because the same results in Visual
Basic occur. I finally had to resort to setting the CommandTimeout
property on the ADODB Connection to 0, just so it would wait until
I've never throught (from what I've heard) that ODBC was fast nor
efficient. Can someone explain to me why ODBC is faster than OLE DB
or is this case an exception to the rule?
Thank you kindly,