【效能優化】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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Oracle DBMS_STATS 包 和 Analyze 命令的區別Oracle
- dbms_stats與analyze分析彙總
- dbms_stat與analyze的區別
- 【效能優化】dbms_stats在ORACLE中的使用優化Oracle
- dbms_stat, dbms_utility與analyze的區別
- Oracle dbms_stats包和analyze 的比較Oracle
- 效能優化漫談之七:效能優化的誤區優化
- 【轉】dbms_stats.gather_table_stats與analyze table 的區別
- async與defer的作用與區別以及阻塞優化優化
- dbms_stats.gather_table_stats與analyze table 的區別[轉貼]
- iOS效能調優之Analyze靜態分析iOS
- 前端效能優化(三)——傳統 JavaScript 優化的誤區前端優化JavaScript
- Nginx安全優化與效能調優Nginx優化
- 效能分析優化的道與術優化
- PHP 7 的革新與效能優化PHP優化
- Golang效能分析與優化Golang優化
- 前端工程與效能優化前端優化
- 資料庫效能調優之始: analyze統計資訊資料庫
- 效能優化指南:效能優化的一般性原則與方法優化
- 高效能MySQL (一):Schema與資料型別優化MySql資料型別優化
- Java 效能優化之——效能優化的過程方法與求職面經總結Java優化求職
- Analyze table對Oracle效能的提升Oracle
- PHP 7革新與效能優化PHP優化
- EBS 中FND_STATS和dbms_stats區別
- 【前端效能優化】vue效能優化前端優化Vue
- analyze index 時validate structure和compute statistics的區別IndexStruct
- 程式效能優化-區域性性原理優化
- Java 執行緒與同步的效能優化Java執行緒優化
- React 同構與極致的效能優化React優化
- 與效能優化有關的幾個程式優化
- Oracle優化案例-hang analyze閱讀方法(三十六)Oracle優化
- FlutterWeb效能優化探索與實踐FlutterWeb優化
- 前端效能優化原理與實踐前端優化
- babel-polyfill使用與效能優化Babel優化
- 資料庫效能優化-索引與sql相關優化資料庫優化索引SQL
- Android效能優化——效能優化的難題總結Android優化
- 前端模組化,AMD與CMD的區別前端
- Flutter的效能優化Flutter優化