Troubleshooting TimeOut Expired Error

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Administration » Troubleshooting TimeOut Expired Error

Troubleshooting TimeOut Expired Error

Rate Topic

Display Mode

Topic Options

Author

Message

rjsapina

Posted Monday, May 25, 2009 1:45 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, February 27, 2013 3:44 AM
Points: 2, Visits: 52

Hi to All,

We got a problem troubleshooting timeout expired error. We are currently using SQL server 2000 and our application programs are developed in VB6.
Our Sever is HP Proliant Dual core with 4 GB memory. We have 20 databases and around 100 users connecting to these databases.

The problem usually occurs during printing of transaction slips to customers and also during scheduled back-ups. We operate 24/7 and the error gives us a head ache. At times, the system works fine but when it occurs, its heavy.

We have already upgraded our network and purchase new switches and still the problem persist.

But there is one thing we have noticed, the data resides on one disk with 136 GB capacity and is not in RAID configuration. The data occupies about 60% of the disk capacity.

Could it be possible that this is causing the timeout expired error?

Please help me out on this.

Thanks,

RJS

Post #722869

nigelrivett

Posted Monday, May 25, 2009 2:13 AM

Old Hand

Group: General Forum Members
Last Login: Monday, January 28, 2013 1:45 AM
Points: 386, Visits: 199

Difficult to say what the issue is.

If you want to look at hardware then do you have separate disks for the tr log and are backups taken to a different disk (and controller)?

If everything is on one disc then anything running will probably slow down everything else.

You might want to look at what the application is doing as optimising that usually has more effect than changing hardware.

Can you keep a copy of the data on another server for the printing? This is more of a batch reporting function and doesn't fit well on an oltp system - simplest would be to replicate to another server - maybe by log shipping or a restore.

Cursors never.
DTS - only when needed and never to control.

Post #722880

rjsapina

Posted Monday, May 25, 2009 3:31 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, February 27, 2013 3:44 AM
Points: 2, Visits: 52

Our data is confined in one disk (MDF and LDF together). Likewise, the backup resides on another disk.

We normally issue transaction slips to our customers and that it should be issued to close the transaction.

Profiler provides stored procedures with select and insert statements.

Thanks for your initial response and I appreciate it very much.

Best Regards,

RJS

Post #722897

« Prev Topic | Next Topic »

Permissions