RE: Slow responses, timeouts, FailDBReader, Deadlocks

That really sounds like a SQL Performance issue.  Sounds like you are
bottlenecked in the IO Subsystem.  Standard SQL approaches are going to
work here I suspect. i.e. Look at Raid5 or Raid10.  The more spindles
the better.  You need to increase your IO throughput.  If you have a
single 120GB hard drive I can definitely see where the problem is coming
from.  Even worse if that is a single IDE hard drive...

Chris

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, January 09, 2004 9:48 AM
To: [email protected]
Subject: [vault-list] Slow responses, timeouts, FailDBReader, Deadlocks
Importance: High

We have just under 50 users.  A single server running Vault and SQL
Server. 4*700mhz procs, a 3GB database.  120GB hard drive. Win2k. yet we
are seeing very slow responses, timeouts etc.

We all use the IDE Add-in and work in a VSS check-out/check-in style.

We all work in the same Repository.

The symptoms exhibit at the same time as SQL produces 1GB+ transaction
logs per 15 minutes at 'busy' times and the Disk Write Queue Length
rockets (up to 90 sometimes).

I've turned off Reverse DNS and put the DB buffer to the default (768),
even rebooted the server.

I've now asked everyone to do GetLatest through the client instead of
the IDE and the transaction logs only reach .5GB.

Any help would be appreciated.

example log attached:

 <<sgvault.log>> 
Kevin.

-- 

------------------------------------------------------------------------
------
HBOS plc, Registered in Scotland No. SC218813. Registered Office: The
Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of
which are regulated by the Financial Services Authority.
========================================================================
======