Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- From: "Daniel Crichton" <msnews@xxxxxxxxxxxxxxxx>
- Date: Fri, 28 Apr 2006 11:43:22 +0100
I've got one PC here running XP Pro SP2 that is acting "weird". I have an
application that uses ADO via an ODBC DSN to do SELECTs and UPDATEs on some
records in a table. Until 2 days ago this application ran perfectly well on
this PC, but now runs very slowly (tests indicate over 100 times slower)
than before. Switching to Named Pipes cures the problem, but I'd rather try
and keep all the machines here configured the same way using TCP/IP. All
other XP Pro and 2000 Pro machines I've run this app on using TCP/IP works
fine.
Another application using the same database code, just dealing with a
different set of records (actually has a larger ForwardOnly recordset in
memory that it loops through to feed the recordset that does the SELECTs and
UPDATEs, around 12000 items compared to 4500 in the one that's running
superslow), runs as quickly as expected using the same DSN when set to
TCP/IP. This is really confusing me - I've checked everything I can think of
on the machine itself (firewall is off, updates applied, MDAC checks out,
etc).
I guess I'm looking for a way to check, and replace with originals, any DLLs
or other files that are used by the SQL Server ODBC driver over TCP/IP that
are not used when connecting via Named Pipes. Any ideas?
Dan
.
- Follow-Ups:
- Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- From: Dave Patrick
- Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- Prev by Date: Re: MDAC 2.8 SP1 Install problem
- Next by Date: Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- Previous by thread: Re: MDAC 2.8 SP1 Install problem
- Next by thread: Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- Index(es):
Relevant Pages
|
|
