메뉴 건너뛰기

Korea Oracle User Group

Guru's Articles

원문 : https://sqlmaria.com/2020/11/03/explain-the-explain-plan-cardinality-estimates/

 

 

Explain the Explain Plan: Cardinality Estimates

In last week’s post, I began a series on how to read and interpret Oracle execution plans by explaining what an execution plan is and how to generate one. This week I’m going to tackle the most important piece of information the Optimizer shares with you via the execution plan, it’s cardinality estimates.

What is a Cardinality Estimate?

A cardinality estimate is the estimated number of rows, the optimizer believes will be returned by a specific operation in the execution plan. The Optimizer determines the cardinality for each operation based on a complex set of formulas that use table and column level statistics as input (or the statistics derived by dynamic sampling). It’s considered the most important aspect of an execution plan because it strongly influences all of the other decisions the optimizer makes.

In part 4 of our series, I share some of the formulas used by the optimizer to estimate cardinalities, as well as showing you how to identify cardinalities in a plan. I also demonstrate multiple ways to determine if the cardinality estimates are accurate.

What can cause a Cardinality Misestimate and how do I fix it?

Several factors can lead to incorrect cardinality estimates even when the basic table and column statistics are up to date. In part 5 of our series, I explain the leading causes of cardinality misestimates and how you can address them.

Next weeks, instalment will be all about the different access methods available to the Optimizer and what you can do to encourage the optimizer to select the access method you want!

Don’t forget this series also covers, how to read an explain plan as well as the different join methods and join orders.

Don’t forget more information on the Oracle Optimizer can always be found on the Optimizer blog.

번호 제목 글쓴이 날짜 조회 수
공지 Guru's Article 게시판 용도 ecrossoug 2015.11.18 188
44 Explain the Explain Plan: Join Methods 명품관 2021.02.10 30
43 Explain the Explain Plan: Access Methods 명품관 2021.02.10 26
» Explain the Explain Plan: Cardinality Estimates 명품관 2021.02.09 16
41 Explaining the Explain Plan – How to Read and Interpret Execution Plans 명품관 2021.02.09 26
40 SQL Window Functions Cheat Sheet 명품관 2020.05.26 154
39 SQL Tuning Workshop 명품관 2020.02.20 1435
38 New initialization parameters, data dictionary views & dynamic performance views in Oracle Database 19c 명품관 2019.02.08 1315
37 More New Features in Oracle Database 19c 명품관 2019.02.08 524
36 New Features of Performance Tuning in Oracle Database 19c 명품관 2019.02.08 532
35 New Features of RAC & ASM in Oracle 19c 명품관 2019.02.08 642
34 New Features of Data Guard in Oracle Database 19c 명품관 2019.02.08 449
33 New Features of Security in Oracle Database 19c 명품관 2019.02.08 3246
32 Patch conflicts 명품관 2019.02.07 439
31 New Features in Oracle Multitenant 19c 명품관 2019.02.07 466
30 New Features of Backup & Recovery in Oracle Database 19c 명품관 2019.02.07 208
29 New Features in Oracle Database 19c 명품관 2019.02.02 375
28 Different MOS Notes for xTTS PERL scripts – Use V4 scripts 명품관 2019.01.29 157
27 V$EVENT_NAME 뷰의 Name 컬럼에 정의된 event name에서 오는 오해 명품관 2017.03.08 205
26 Can I apply a BP on top of a PSU? Or vice versa? 명품관 2016.06.01 287
25 How to change the database name in 12c 명품관 2016.05.31 325
위로