Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Tue, 2 May 2006 15:58:09 +0100
All XP patches had been installed. What I'm at a loss to explain is whyone
copy of the app works, yet the other doesn't. I have also tested the copysame
that has problems on this machine with another that is near identical -
hardware, same patches - and it doesn't have a problem. I guess I'll justto
have to stick with Named Pipes for now and try to nail down the issue some
other time when Named Pipes no longer works properly ... not the ideal
situation, but this machine is in use 24/7 and I don't have another spare
use while attempting to find the source of the problem. I was hopingsomeone
else might have seen something similar and be able to give me a starting
point. If I find the cause I'll post the solution.
I sympathise. I have been in this situation. There has to be a difference.
Is it worthwhile to run some TCPIP configuration diagnostics?
I would be looking for static diagnostics - something to run on both
machines and try and isolate any factor that is different.
Stephen Howe
.
- References:
- Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- From: Stephen Howe
- Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- From: Daniel Crichton
- Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- Prev by Date: Re: (SQL) Using Variable in select command
- Next by Date: Re: Remove apostrophe from text (export to Excel)
- Previous by thread: Re: Slow access on XP using ADO with ODBC to SQL Server 2000 - any ideas?
- Next by thread: Re: (SQL) Using Variable in select command
- Index(es):