91超碰碰碰碰久久久久久综合_超碰av人澡人澡人澡人澡人掠_国产黄大片在线观看画质优化_txt小说免费全本

溫馨提示×

溫馨提示×

您好,登錄后才能下訂單哦!

密碼登錄×
登錄注冊×
其他方式登錄
點擊 登錄注冊 即表示同意《億速云用戶服務條款》

How to Specify an INDEX Hint oracle官方文檔

發布時間:2020-08-11 20:35:25 來源:ITPUB博客 閱讀:198 作者:dl_lang 欄目:關系型數據庫
How to Specify an INDEX Hint (Doc ID 50607.1)
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.2 [Release 9.2 to 11.2]
Information in this document applies to any platform.
Purpose

This article explains how to specify index hints successfully.
Troubleshooting Steps

The format for an index hint is:
select /*+ index(TABLE_NAME INDEX_NAME) */ col1...

There are a number of rules that need to be applied to this hint:

    The TABLE_NAME is mandatory in the hint
    The table alias MUST be used if the table is aliased in the query
    If TABLE_NAME or alias is spelled incorrectly then the hint will not be used.
    The INDEX_NAME is optional.
    If an INDEX_NAME is entered without a TABLE_NAME then the hint will not be applied.
    If a TABLE_NAME is supplied on its own then the optimizer will decide which index to use based on statistics.
    If the INDEX_NAME is spelt incorrectly but the TABLE_NAME is spelled correctly then the hint will not be applied even though the TABLE_NAME is correct.
    If there are multiple index hints to be applied, then the simplest way of addressing this is to repeat the index hint syntax for each index e.g.:
    SELECT /*+ index(TABLE_NAME1 INDEX_NAME1) index(TABLE_NAME2 INDEX_NAME2) */ col1...
     
    Remember that the parser/optimizer may have transformed/rewritten the query or may have chosen an access path which make the use of the index invalid and this may result in the index not being used.

Legacy Note: As long as the index() hint structure is correct this will force the use of the Cost Based Optimizer (CBO). This will happen even if the alias or table name is incorrect.

Examples

The examples below use a table CBOTAB with a unique single column index called CBOTAB1 on column COL1.

Correct hint to force use of the index:

 explain plan for select /*+ index(cbotab) */ col1 from cbotab;
 explain plan for select /*+ index(cbotab cbotab1) */ col1 from cbotab;
 explain plan for select /*+ index(a cbotab1) */ col1 from cbotab a;

Query Plan
--------------------------------------------------------------------------------
SELECT STATEMENT   [CHOOSE] Cost=151
  INDEX FULL SCAN CBOTAB1 [ANALYZED]  Cost=151 Card=10000 Bytes=100000

 

    The TABLE_NAME is mandatory in the hint.
    In the following example the TABLE_NAME was omitted so the index was not used.

    SQL>  explain plan for select /*+ index() */ col1 from cbotab;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=10
      TABLE ACCESS FULL CBOTAB [ANALYZED]  Cost=10 Card=10000 Bytes=100000

    The INDEX_NAME is optional.
    Both of the following examples use the index:

     explain plan for select /*+ index(cbotab) */ col1 from cbotab;
     explain plan for select /*+ index(cbotab cbotab1) */ col1 from cbotab;

    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=151
      INDEX FULL SCAN CBOTAB1 [ANALYZED]  Cost=151 Card=10000 Bytes=100000

    The table alias MUST be used if the table is aliased in the query

    SQL>  explain plan for select /*+ index(cbotab) */ col1 from cbotab mytable;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=10
      TABLE ACCESS FULL CBOTAB [ANALYZED]  Cost=10 Card=10000 Bytes=100000

    Correct use of alias in hint:

    SQL>  explain plan for select /*+ index(mytable) */ col1 from cbotab mytable;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=151
      INDEX FULL SCAN CBOTAB1 [ANALYZED]  Cost=151 Card=10000 Bytes=100000

    If TABLE_NAME or alias is spelled incorrectly then the hint will not be used.

    SQL>  explain plan for select /*+ index(COBTAB) */ col1 from cbotab;
    SQL>  explain plan for select /*+ index(MITABLE) */ col1 from cbotab mytable;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=10
      TABLE ACCESS FULL CBOTAB [ANALYZED]  Cost=10 Card=10000 Bytes=100000

    If an INDEX_NAME is entered without a TABLE_NAME then the hint will not be applied.

    SQL>  explain plan for select /*+ index(cbotab1) */ col1 from cbotab;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=10
      TABLE ACCESS FULL CBOTAB [ANALYZED]  Cost=10 Card=10000 Bytes=100000

    If a TABLE_NAME is supplied on its own then the optimizer will decide which index to use based on statistics.

    explain plan for select /*+ index(cbotab) */ col1 from cbotab;

    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=151
      INDEX FULL SCAN CBOTAB1 [ANALYZED]  Cost=151 Card=10000 Bytes=100000

    If the INDEX_NAME is spelt incorrectly but the TABLE_NAME is spelt correctly then the hint will not be applied even though the TABLE_NAME is correct.

    SQL>  explain plan for select /*+ index(cbotab COBTAB1) */ col1 from cbotab;
    Query Plan
    --------------------------------------------------------------------------------
    SELECT STATEMENT   [CHOOSE] Cost=10
      TABLE ACCESS FULL CBOTAB [ANALYZED]  Cost=10 Card=10000 Bytes=100000


     
向AI問一下細節

免責聲明:本站發布的內容(圖片、視頻和文字)以原創、轉載和分享為主,文章觀點不代表本網站立場,如果涉及侵權請聯系站長郵箱:is@yisu.com進行舉報,并提供相關證據,一經查實,將立刻刪除涉嫌侵權內容。

AI

大渡口区| 嫩江县| 古田县| 霞浦县| 株洲县| 六盘水市| 深水埗区| 津南区| 黑河市| 巴马| 和硕县| 军事| 黄陵县| 西昌市| 南雄市| 金山区| 两当县| 将乐县| 酉阳| 宁安市| 麟游县| 大石桥市| 江北区| 土默特左旗| 宜川县| 宝应县| 泸溪县| 宁陕县| 阜康市| 宁夏| 乐亭县| 茌平县| 商城县| 弋阳县| 齐河县| 湘潭县| 宁海县| 平罗县| 江永县| 嘉兴市| 印江|