Re: ADO Behaving VERY badly...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

ADO classic and ADO.NET are (as you well know) very different in their
approach to fetching and persisting client-side data. However, if code works
on one system and not another I look for differences in the installed code.
In a .NET application this is pretty straightforward. That's not the case
with MDAC. It's not hard to disturb the MDAC stack as we've seen in
countless cases. I would run Component Checker (www.microsoft.com/data) to
verify that the stack is the same on both the working and slower systems.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

"cvelazquez62" <chris#boerne,biz> wrote in message
news:B3B1B5B3-499D-4799-8215-CC590FF6385E@xxxxxxxxxxxxxxxx
> I'm seeing weird 2-second pauses when using ADO (MDAC 2.8) with MSDE
> 2000A.
> This happens on some machines but not others. I wrote small test programs
> in
> VB6 and VBScript to retrieve ADO Recordsets for a number of individual SQL
> SELECT statements. A few statements will execute, then there will be
> about a
> two second pause, and a few more statements will execute, then another
> pause,
> and so on. It's not dependent on the SQL statement being issued, it will
> even pause on an SQL request for a single record in a table containing
> only
> one record, requested with the WHERE clause as primary key!
>
> I don't think the database is the problem. If I write the same program in
> C# using DataSets, the SQL statements execute rapidly from start to finish
> with no pauses. This database is pretty tight, normalized, and indexed
> nicely, and only has about 40 tables, and the test database has an MDF
> file
> that's only 13 MB. The WHERE clauses of my statements are all on indexed
> columns.
>
> It doesn't seem to depend on the computer's speed either. I see the
> problem
> on my wife's P4 1.8 GHz w/256MB, and also on my client's 3.4 GHz P4 w/1GB
> RAM. My pokey 2.0 GHz P4 laptop w/512 and my test box 2.0 GHz w/1GB seem
> to
> work fine. All systems are running XP SP2 with patches up to date.
>
> This database is being used as the back end for both VB6 and C# desktop
> applications, so I need to get this working using ADO "Classic". On
> machines
> where this problem manifests itself, the VB6 app is so slow that it's
> unusable. I can't do a total rewrite in .NET right now (though I plan to
> in
> the future).
>
> If anyone has any clues as to WTF is going on here, I sure would
> appreciate
> it!
>
> Thanks,
> Chris


.

Relevant Pages

  • Re: Add field to jet database table in ADO
    ... Run this SQL statement against your database using ADO and it will add a ... "Michael Malinsky" wrote in message ... > I've been working through some code on the MS KB on how to use ADO to ... > and manipulate a jet database. ...
    (microsoft.public.excel.programming)
  • Out of Memory Issue when getting records
    ... I'm using ADO and SQL to retreive a set of records. ... works great until to do a join with another database to show the additional ... Here is my SQL Statement: ...
    (borland.public.delphi.database.ado)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)
  • Re: Is ADO Dead (3)?
    ... The Design of ADO ... ADO uses a single object, the Recordset, as a common representation for ... a forward-only stream of results from a database, ... where data is updated at the data source or cached locally as with the ...
    (comp.databases.ms-access)