- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 62 Insurance
- 536K On-Premises Infrastructure
- 138.2K Analytics Software
- 38.6K Application Development Software
- 5.7K Cloud Platform
- 109.4K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
peek LAST_ANALYZED for SYSDATE range predicates for selectivity estimation/optimization
Statistics get STALE for the most recent time period quickly by nature as there is (suppositionally) no extrapolation applied by the optimizer,
so selectivity estimations for predicates involving SYSDATE relations tend to diverge more and more with aging statistics.
Maybe an easy and reliable approach would be to use the LAST_ANALYZED date of the involved column/table instead of the actual SYSDATE for the optimizations selectivity estimation.
"The other aspect that always changes is time. People have tried but it’s very difficult to stop time. When things worked well, it was at a different point in time than now when things have suddenly gone wrong."