Updating statistics in oracle who is john gotti agnello dating
If there is very little modification () to the data, then you could have a more infrequent schedule for the update statistics job.One way to find out if your statistics are stale is to look at the execution plans and if you estimated rows greatly differ from your actual rows returned then that is a good indication that the interval needs to be upped.When that operation happens, statistics are automatically updated (provided that isn't turned off for the index).Exactly how often you should be updating statistics depends greatly on how much data modification your indexes and data is receiving.You can examine the statistics (including time since the last update) by querying the systabstats and sysstatistics table, or by using the optdiag utility from the OS prompt.Does updating statistics cause locking and contention?In your case, you're going the other way and a bit of trial may be in order for you.Update statistics weekly, and if you're starting to see the tell-tale signs of stale stats then go from there.
In earlier versions of ASE, this may have sometime happened; however, in the newer releases of ASE, locking is minimal and this should not be a significant concern.
NOTE In high-volume environments, you can update statistics on a restored database, and then import them into the production server using the optdiag utility, but that’s a lot more work.
Options for updating statistics ASE provides a number of options for updating statistics, depending on the specific needs you have.
this solution only rebuilds/reorganize and updates what is needed this way you might shortenthe time your maintinance plan takes and also save a hole lot of log space.. In your original post, you said that users are seeing a performance degredation due to this maintenance plan.
Is there no other time to run this maintenance plan? I see that your plan encompasses index reorganization, when are you rebuilding indexes?