Performance problems

Hi,
I have an OLTP database and the users get timeout messages
in the mornings when they initially start the application
and it is fine for the rest of the day.I have looked into
all other applications and users and found that this
application is only the problem.I have been monitoring the
performance monitor and found out that there are some
latches at this time and the avg disk queue length is very
high during this time.It only happens to a couple of
procedures in the whole application .
I am running SQL 2000 Ent with cluster,4 CPU and 6Gb of
RAM.
Any help is really appreciated.
Thanks
SatAre backups happening at that time ?
Greg Jackson
PDX, Oregon|||I woudl consider using SQL Profiler to see what else is happening at this
time.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
<anonymous@.discussions.microsoft.com> wrote in message
news:6fc101c40228$07372b60$a301280a@.phx.gbl...
> Hi,
> I have an OLTP database and the users get timeout messages
> in the mornings when they initially start the application
> and it is fine for the rest of the day.I have looked into
> all other applications and users and found that this
> application is only the problem.I have been monitoring the
> performance monitor and found out that there are some
> latches at this time and the avg disk queue length is very
> high during this time.It only happens to a couple of
> procedures in the whole application .
> I am running SQL 2000 Ent with cluster,4 CPU and 6Gb of
> RAM.
> Any help is really appreciated.
> Thanks
> Sat
>
>|||The backups are not running and i have eliminated other users possibility also.I have tried running profiler earlier and th
users are having some problems(performance) even if i run on a workstation.Any other help is appreciated.But i will try t
run the profiler again
Thank
Sa|||Sorry, I don't have an answer, only some questions that you might want to ask yourself
Are you sure the problem IS the database
You say this this problem only happens to one certain application, but not others
Are the other applications connect to the same SQL Server node?
Do they all have the same architeture (ASP, COM+, thick clients or thin clients).
Is the time out on the database, or is it the application? So, if you have using object pooling, the problem might be a time-out waiting for the COM object to be created in the pool.
Or if using database connection pooling, this might be the problem. If connection pooling is being used, you might be able to do a couple of actions, and then a free connection isn't avalaible for the next transaction, so you get the time out
The high disk queue length; I take it this is on the disk array with the databases on. What else is on disk array, or is it only the DB
Has the node been running some memory heavy job in the evening, not related to the SQL Server ? What is the SQL Server memory allocation in the morning before they start login in ? What is the Buffer Cache Hit Ratio at this time of day ?