Re: 100% CPU Util on Simple Update Query
From: Jesse Beveridge (jesse_at_nospam.nospam)
Date: 02/09/05
- Next message: MGFoster: "Re: SELECT GROUP BY smalltimedate"
- Previous message: Joel H: "100% CPU Util on Simple Update Query"
- In reply to: Joel H: "100% CPU Util on Simple Update Query"
- Next in thread: Joel H: "Re: 100% CPU Util on Simple Update Query"
- Reply: Joel H: "Re: 100% CPU Util on Simple Update Query"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 08 Feb 2005 21:12:44 -0700
What is the actual statement? Is there a where clause on it?
-- Jesse
On Tue, 8 Feb 2005 19:51:02 -0800, Joel H
<JoelH@discussions.microsoft.com> wrote:
>We just moved a database from SQL7 to 2000.I ran sp_updatestats after
>updating. One table has about 4000 rows, a single column primary key of type
>t_Ticker which is char 10. A query wants to update several items in one row.
>A sample is
>UPDATE tblTable set CharColumn='12345'.
> Yet even that simple query ties up the machine at 100% cpu, and doesn't
>finish.
>It ran fine on SQL 7.
>When I was trying to see if it was an index problem, by removing and
>replacing the primary key, it would occasionally (not reliably) run quickly,
>but the next time might fail again. I ran the query as part of an sp, but
>also from the analyser.
>The development machine is a 2 GHz, 750MB desktop, but it also fails on the
>production machine. Sql2000 is at SP3.
>TIA for any suggestions.
- Next message: MGFoster: "Re: SELECT GROUP BY smalltimedate"
- Previous message: Joel H: "100% CPU Util on Simple Update Query"
- In reply to: Joel H: "100% CPU Util on Simple Update Query"
- Next in thread: Joel H: "Re: 100% CPU Util on Simple Update Query"
- Reply: Joel H: "Re: 100% CPU Util on Simple Update Query"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|