High CPU usage after backup

We've noticed on our server that the CPU usage goes from its normal 60% to
90% during a backup job, and stays at 90% even after the job is complete.
The backup job takes 30 seconds to a minute to complete, but CPU usage stays
at 90% (of which the "sqlservr.exe" process is taking 70%). The backup job
updates the statistics and backs up the transaction log.
The "really" strange thing I've found, is that by just running Enterprise
Manager and accessing the Properties dialog of the server (I don't need to
toggle any settings), will cause CPU usage to go back down to it's normal
60%. This seems to work whether I'm doing this on the server via Remote
Desktop, or using my local Enterprise Manager to connect to the server
remotely.
Has anyone observed this occurring before?
We're running SQL Server 2000 Standard Edition SP3 (I know we need to update
this), on Windows Server 2003. Server is a Xeon 2.8 with 2gb ram.
In terms of database size, its at 1gb, with 4gb allocated. Transaction log
is at 2gb with 7gb allocated.Hi
I have not experienced this, but if this was on a SAN my guess would be a
replication issue/hardware bottleneck. Check out the perfmon counters and SAN
stats to see if there are problems.
Moving the latest service pack/patch level may be useful.
John
"Ken" wrote:
> We've noticed on our server that the CPU usage goes from its normal 60% to
> 90% during a backup job, and stays at 90% even after the job is complete.
> The backup job takes 30 seconds to a minute to complete, but CPU usage stays
> at 90% (of which the "sqlservr.exe" process is taking 70%). The backup job
> updates the statistics and backs up the transaction log.
> The "really" strange thing I've found, is that by just running Enterprise
> Manager and accessing the Properties dialog of the server (I don't need to
> toggle any settings), will cause CPU usage to go back down to it's normal
> 60%. This seems to work whether I'm doing this on the server via Remote
> Desktop, or using my local Enterprise Manager to connect to the server
> remotely.
> Has anyone observed this occurring before?
> We're running SQL Server 2000 Standard Edition SP3 (I know we need to update
> this), on Windows Server 2003. Server is a Xeon 2.8 with 2gb ram.
> In terms of database size, its at 1gb, with 4gb allocated. Transaction log
> is at 2gb with 7gb allocated.
>
>