【效能優化】ANALYZE 與DBMS_STATS的區別
From asktom
-------------
you can import/export/set statistics directly with dbms_stats
it is easier to automate with dbms_stats (it is procedural, analyze is just a command)
dbms_stats is the stated, preferred method of collecting statisttics.
dbms_stats can analyze external tables, analyze cannot.
DBMS_STATS gathers statistics only for cost-based optimization; it does not gather other
statistics. For example, the table statistics gathered by DBMS_STATS include the number
of rows, number of blocks currently containing data, and average row length but not the
number of chained rows, average free space, or number of unused data blocks.
dbms_stats (in 9i) can gather system stats (new)
ANALYZE calculates global statistics for partitioned tables and indexes instead
of gathering them directly. This can lead to inaccuracies for some statistics, such as
the number of distinct values. DBMS_Stats won't do that.
Most importantly, in the future, ANALYZE will not collect statistics needed by
the cost-based optimizer.
-------------
you can import/export/set statistics directly with dbms_stats
it is easier to automate with dbms_stats (it is procedural, analyze is just a command)
dbms_stats is the stated, preferred method of collecting statisttics.
dbms_stats can analyze external tables, analyze cannot.
DBMS_STATS gathers statistics only for cost-based optimization; it does not gather other
statistics. For example, the table statistics gathered by DBMS_STATS include the number
of rows, number of blocks currently containing data, and average row length but not the
number of chained rows, average free space, or number of unused data blocks.
dbms_stats (in 9i) can gather system stats (new)
ANALYZE calculates global statistics for partitioned tables and indexes instead
of gathering them directly. This can lead to inaccuracies for some statistics, such as
the number of distinct values. DBMS_Stats won't do that.
Most importantly, in the future, ANALYZE will not collect statistics needed by
the cost-based optimizer.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22664653/viewspace-672392/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- async與defer的作用與區別以及阻塞優化優化
- Analyze table對Oracle效能的提升Oracle
- 資料庫效能調優之始: analyze統計資訊資料庫
- 效能分析優化的道與術優化
- Nginx安全優化與效能調優Nginx優化
- Golang效能分析與優化Golang優化
- 效能優化指南:效能優化的一般性原則與方法優化
- 高效能MySQL (一):Schema與資料型別優化MySql資料型別優化
- Oracle優化案例-hang analyze閱讀方法(三十六)Oracle優化
- MongoDB aggregate效能優化與排序MongoDB優化排序
- 【前端效能優化】vue效能優化前端優化Vue
- Java 效能優化之——效能優化的過程方法與求職面經總結Java優化求職
- 程式效能優化-區域性性原理優化
- Android效能優化——效能優化的難題總結Android優化
- Java 執行緒與同步的效能優化Java執行緒優化
- Ajax、fetch、axios的區別與優缺點iOS
- FlutterWeb效能優化探索與實踐FlutterWeb優化
- 前端效能優化原理與實踐前端優化
- babel-polyfill使用與效能優化Babel優化
- 資料庫效能優化-索引與sql相關優化資料庫優化索引SQL
- Linux的優缺點,Linux與windows的區別LinuxWindows
- Flutter的效能優化Flutter優化
- UIImageView UIView圓角與效能之間的研究與優化UIView優化
- Oracle效能優化方法論的發展之一:基於區域性命中率分析的效能優化方法Oracle優化
- [精選] SQL中的IN與NOT IN、EXISTS與NOT EXISTS的區別及效能分析SQL
- 效能優化優化
- Flutter 應用效能檢測與優化Flutter優化
- 前端效能優化的點前端優化
- iOS 效能優化的探索iOS優化
- 前端效能優化(JS/CSS優化,SEO優化)前端優化JSCSS
- spring不同配置方式的區別與優先順序Spring
- Android 效能優化 ---- 啟動優化Android優化
- Android效能優化----卡頓優化Android優化
- [效能優化]DateFormatter深度優化探索優化ORM
- 前端效能優化 --- 圖片優化前端優化
- 效能優化|Tomcat 服務優化優化Tomcat
- ??與?:的區別
- HTTP前端效能優化(壓縮與快取)HTTP前端優化快取
- android效能評測與優化-記憶體Android優化記憶體