Huh?

Post #415,924 by crazy 12/6/16 8:49:20 PM 12/6/16 8:49:20 PM Reply	Huh? One off or going to keep happening. You say both. The key issue is unless you are paying by compute cycles, assuming there is nonpeak times, scheduled stats collection is a no cost win. And if there is never a slow time, then run it anyway but with reduced priority.
Post #415,926 by drook 12/6/16 9:45:02 PM 12/6/16 9:45:02 PM Reply	What I mean is we'll keep having one-off events We've never done this event for this client at this venue before. I find it hard to believe the things that matter to query performance would change so radically from event to event. Volume should be the major factor, so if we handle $x TPS we should be good for anything < $x. That doesn't seem to be true. -- Drew
Post #415,933 by crazy 12/7/16 11:30:55 AM 12/7/16 11:30:55 AM Reply	Absolutely not TPS is total volume. Which nothing to do with data skew. New or changing field contents can dramatically change which indexes to use or how to use them, or to use them at all, which modifies query plan.
Post #415,992 by malraux 12/13/16 9:07:05 AM 12/13/16 9:07:05 AM Reply	This. The larger the data load, the bigger the potential change in index distribution. Regards, -scott Welcome to Rivendell, Mr. Anderson.

Welcome to IWETHEY!