Backing up transaction logs gives poor performance.
- From: "SW" <anonymousgravy@xxxxxxxxxxx>
- Date: Thu, 19 Jul 2007 23:12:34 +0100
Hi,
I have a problem with SQL server being very slow to access and use while I'm backing up transaction logs. I'm backing up the logs every half hour, and it makes the whole thing run so slowly it's driving the users nuts. It puts the application into a spin while the logs are being backed up and it's being used by a lot of people. If there's less people its still noticeable but not as severe.
Its SQL 2000, on a W2003 server, XP clients. Server has twin Xeon 2.8 cpus with 4GB RAM and a RAID 5 array. There's 2 instances of SQL server hosting 2 separate, different applications. The database sizes are varied. On one of the apps there's a database with a 11.5GB .mdf file, and a 6GB .ldf file. Transaction log backup files from this database are typically about 20MB while the application is busy. The users of both apps complain of the same problem - intermittent slowness so bad it sometimes makes the app unusable.
The log backup seems to cripple the entire machine.
Where do I start to cure this problem?
Is there a way I can get the maintenance plan to use less cpu? Or is it more likely a memory problem?
Any help appreciated, Thanks in advance,
SW
.
- Follow-Ups:
- Re: Backing up transaction logs gives poor performance.
- From: Tibor Karaszi
- Re: Backing up transaction logs gives poor performance.
- Prev by Date: Re: SP2 admin install
- Next by Date: Licencing?
- Previous by thread: New to SQl and trying to create a Full Text Index in MSSQL 2000 on Windows SBS 2003
- Next by thread: Re: Backing up transaction logs gives poor performance.
- Index(es):
Relevant Pages
|
Loading
