Update Statistics hitting 100% CPU
I have an Update Stats job setup which runs everyday at 4 AM and is pegging the CPU to 100% for a few secs. The DB is around 14 GB and SQL 2005/ Win 2k3.
This is a custom job with simple login update statistics [tblName] with Full Scan
I also tried using maintenance plan job, but even that is causing CPU spikes.
I tried to use MAXDOP in the command but was encountering Syntax errors.
Is there a way to run this job to ensure that there are no CPU spikes to 100%.