Re: ADO and XP

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 10:17:08 -0800

Sure. I expect the XP system does not have the resources needed to get the
tasks done before the governor kicks in. If the XP system does not have
enough RAM to cache the SPs or data, it has to wait for disk IO for those
tasks that need it. More RAM means fewer disk hits. It could also mean that
the processor is not as fast or busy with other operations--this can cause
the same behavior.
You might try to optimize the SP by examining how the query plan is being
created for each set of parameters. Remember that the query plan used is a
function of whether or not it's cached and the parameters provided. I
discuss this in my session at DevConnections in Orlando later this month.

hth 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Eric" <anonymous@discussions.microsoft.com> wrote in message
news:39B2A80D-4279-41F7-A085-5256E0659BC8@microsoft.com...
> We have a VB6 app connecting via ADO to an MSDE 1.0 database that runs
without problems in NT4.0 and Win2000 environments but consistantly slows
down in XP.  Performace differences are on the order of 7 to 10 stored
procedures (same stored procedure, different parameters) executing every
second in NT/2000, but slowly degrading in an XP environment from the 7 to
10 /second down to 1 per minute.  In all environments the app writes a 250
byte block to an open file on a hard drive between each execution of the
stored procedure.  Any ideas why we experience the slowdown but no command
timeouts in the XP environment?  The VB6 app was compiled against ADO 2.5.
>
> Thanks

Relevant Pages