ms sql server response is slow

Hi ,

i have ms access client program connecting to sql server 2000 wif sp3a
running on windows 2000 server

the user is complaining that the response from the client program is slow

i have check the current activity and there's no much user connected and
there's no lock/blocking process

where could i check further to determine the cause ?

tks & rdgs

You have only begun to scrape the surface of your issue.

There is a lot more that needs to be known to pinpoint anything.

1. Is MS Access using ADO to connect, or is it using the older DAO libraries
to connect?

2. If you are calling a stored procedure, is that individual sproc slow?
Are the tables indexed correctly?

You have to understand where the issue is with the user, and observe exactly
what they are doing - maybe it is the "way" they are doing the operation?

Trace it from their point of view, backwards through the various layers down
to the database.  It may be something in the MS Access VBA code that is
causing the contention.



"maxzsim" <maxzsim@discussions.microsoft.com> wrote in message
news:19F3E7F8-E9B6-4B93-8368- 9B9FE46F813B@microso
ft.com...
> Hi ,
>
> i have ms access client program connecting to sql server 2000 wif sp3a
> running on windows 2000 server
>
> the user is complaining that the response from the client program is slow
>
> i have check the current activity and there's no much user connected and
> there's no lock/blocking process
>
> where could i check further to determine the cause ?
>
> tks & rdgs

Hi,

i am connected to the SQL server via odbc ver 3.52.

the problem started when the user got the connection failed error while
running the program with SQL State HYP000

i looked into the articles for theis connection failed but it seems not
related in my case
rdgs

"news.microsoft.com" wrote:

> You have only begun to scrape the surface of your issue.
>
> There is a lot more that needs to be known to pinpoint anything.
>
> 1. Is MS Access using ADO to connect, or is it using the older DAO librari
es
> to connect?
>
> 2. If you are calling a stored procedure, is that individual sproc slow?
> Are the tables indexed correctly?
>
> You have to understand where the issue is with the user, and observe exact
ly
> what they are doing - maybe it is the "way" they are doing the operation?
>
> Trace it from their point of view, backwards through the various layers do
wn
> to the database.  It may be something in the MS Access VBA code that is
> causing the contention.
>
>
>
> "maxzsim" <maxzsim@discussions.microsoft.com> wrote in message
> news:19F3E7F8-E9B6-4B93-8368- 9B9FE46F813B@microso
ft.com... 
>
>
>