• Eddie Wuerch (10/13/2015)


    I'm not sure about SQL Server 2012, but with versions prior, old stats on tables with 1 billion+ rows would cause shocking CPU consumption during compilation.

    Once stats get updated, CPU consumption would drop on those queries dramatically, even though we were sampling .0017% in order to get the scan to complete.

    If you keep more current stats on those big tables, you should see some CPU perf improvement.

    -Eddie

    Thanks for reply.

    That's exactly what I was thinking. In fact, I can see those small CPU spikes after I deployed. I use RedGate though, so I will be able to monitor over time.