I've got some Siebel consultants busy importing data into a new sql box. They've been complaining about inconsistent performance and timeouts. My initial reaction was that it was there software.. however I've seen the problem and its definitely on the sql server side. Heres are some details:
- SQL Box: Compaq ML370, 1.2 GB ram, 1 ghz processor
- siebel database: 500 mb
The statement that I've just seen a timeout on was the following:
UPDATE dMmarriotUTtakeonTXN SET Status = 4 WHERE (Status = 0 or Status is null) AND ID = 44068
This table has about 50k records and it has an index on ID. The update also only acts on 1 record.
Looking at their log the process flies through - 4 or 5 transactions a second until suddenly a timeout. I cannot find any similarities between timeouts. There is nothing else running on this box, log backups etc are not running, theres plenty of disk space allocated, nothing funny happening on the network, no error message in the logs.
Any ideas on where I even start trying to look at this?