Hi folks. I am experiencing something "weird" in one of my environments. I have a Â±300 GB database, against which batch- and on-line transactions takes place. The "auto update statistics" function is switched on, and weekly an "Update Statistics" gets run on the whole database. We started to realize that after the weekly "update stats" job was run, certain batch jobs' run-time suddenly increases with about 400% (8 minutes to 54 minutes.. to name one example). I tested this in our Pre-Production environment as well, and got the same results. A definite increase in the run-time directly after the "update stats" job. Have any of you had similar experiences? What could the reason for this be? Would it be wise to then rather cancel the "update stats" job, seeing that we do have the "auto update statistics" on, and we do re-indexing on a monthly basis, which would also update the stats. By the way... after the re-indexing, the timing still looks good/better, in spite of stats being updated then? Please throw some ideas/thoughts at me. Ciao.