SQL 2K / WINDOWS 2003 SERVER
I have a box with 2 SQL INSTANCES and each instances with few databases.
Memory is setup to 'Use a fix memory size' and setup with half and one GB
each .
Almost 250 GB free hard-disk space and both instances using 4 processors.
I have different SQL jobs running on each instances.
My issue is , few jobs which usually runs within 4-5 hrs, running for 12-15
hrs and this is not happening always.
Checked for SQL LOCKS and found NONE.
Please advice me , how to trouble-shoot this '
Rgds
MS-USERHi
Without knowing the nature of the jobs it is hard to give detailed advice,
but I would start by looking at performance monitor and try and see if there
is a bottleneck. Your may well have contention on the discs as this is a
common resource that each instance will be competing with, therefore disc
queue lengths, also if your logs and data are on the same set of discs there
potentially there would be problems even with a single instance. Another are
a
that may cause problems is processor affinity. You may want to change the
affinity mask and see if that helps or use the MAXDOPS hint on your queries.
You may want to read the SQL Server 2000 Performance Tuning Technical
Reference Manual ISBN ISBN 0-7356-1270-6 and Inside SQL Server 2000 by Kalen
Delaney ISBN 0-7356-0998-5
John
"MS User" wrote:
> SQL 2K / WINDOWS 2003 SERVER
> I have a box with 2 SQL INSTANCES and each instances with few databases.
> Memory is setup to 'Use a fix memory size' and setup with half and one GB
> each .
> Almost 250 GB free hard-disk space and both instances using 4 processors.
> I have different SQL jobs running on each instances.
> My issue is , few jobs which usually runs within 4-5 hrs, running for 12-1
5
> hrs and this is not happening always.
> Checked for SQL LOCKS and found NONE.
> Please advice me , how to trouble-shoot this '
> Rgds
> MS-USER
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment