Database Server running slow. I used SP_WHO2 ACTIVE and the result
has many of
XXXX SA RUNNABLE MASTER AWAITING
COMMAND........
(XXXX is spid)
and they stay for couples seconds.
Last week , the server was running fine and during weekend ,none
of errors record in Windows
event log or SQL Server log.
Server is Windows 2003 server with 4 CPUs of xeon , 4 GB of memory
and
MSSQL SERVER 200 SP4.
I found out that every runnable master db tasks has shared lock on
key of
'master.dbo.sysxlogins.sysxlogins' object
Is this the problem of slow running database server?
Please advice.
Peeud
Quote:
Originally Posted by
Database Server running slow. I used SP_WHO2 ACTIVE and the result
has many of
>
XXXX SA RUNNABLE MASTER AWAITING
COMMAND........
(XXXX is spid)
>
and they stay for couples seconds.
As long as these entries only stay for a couple of seconds it means
that whatever is opening these connections is closing it again. I would
start to worry if these connections don't close and are increasing in
numbers.
Also as long as the BlkBy column doesn't have an entry then it means
that the these processes aren't being blocked, which is a good thing.
Quote:
Originally Posted by
I found out that every runnable master db tasks has shared lock on
key of
'master.dbo.sysxlogins.sysxlogins' object
>
Is this the problem of slow running database server?
When you mean slow running database server are you referring to
Windows, or SQL Server when you pull a query? If you are referring to
Windows, use Windows Task Manager to ensure that there are no processes
using large amounts of CPU or Memory resources. If you are referring to
SQL Server, use SQL Profiler to determine what queries are running and
see if some performance tuning can be done on those tables.
Regards,
Louis
