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@.microsoft.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 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@.microsoft.com...
>
>
sql
Showing posts with label slow. Show all posts
Showing posts with label slow. Show all posts
Wednesday, March 28, 2012
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 & rdgsYou 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@.microsoft.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@.microsoft.com...
>
>
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 & rdgsYou 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@.microsoft.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@.microsoft.com...
>
>
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 & rdgsYou 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@.microsoft.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 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@.microsoft.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
>
>
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 & rdgsYou 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@.microsoft.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 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@.microsoft.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
>
>
Monday, March 26, 2012
Ms Sql Server Giving Timeout Expired
We are using MS SQL 2000 it is giving timeout expired proble Intermittently and the users getting slow response in the Transactions.
Need Help to solve the same.The ConnectionTimeout property of the Connection object, should be increased as much as is needed (applicable to VB6, .Net). I think that any languagae has a similar property.|||Take also in account this method .|||Hi,
Need Help to solve the same.The ConnectionTimeout property of the Connection object, should be increased as much as is needed (applicable to VB6, .Net). I think that any languagae has a similar property.|||Take also in account this method .|||Hi,
In some servers, if the Select statement is run with out specifying WITH (NOLOCK) then it will throw timeout expired.
Suppose you run the following query from your application
Select * from emp;
then it will throw time out expired
Please use
Select * from emp WITH (NOLOCK);
then it wont expire. I am not sure of which server setting that causes this problem.
The application will be slow if some one is trying to run a select statement without using "WITH (NOLOCK)"
Try to avoid users from executing the Select statement, which poses this problem.
Also if many Users are accessing the DB, then we should give some time for the DB to process it. If many processes queues up, then finally some will expire.This is purely due to the load on the DB.
Also monitor the performance of DB, some stored procedures that we write will eat up all DB resources because of which the application will hang up until that is executed.
It may also be due to increase in number of users using the application.
Hope this will be useful.|||Ye, good observation, but I think that it's not always recommended to use NOLOCK, and for any Select. Eventually for special queries where it's expected to take a long time.
Subscribe to:
Posts (Atom)