oracle hints

今天是2013-10-08，对于oracle hint有很多，具体可以参考联机手册：

http://docs.oracle.com/cd/E11882_01/server.112/e41084/sql_elements006.htm#BABIJGJF

http://docs.oracle.com/cd/E11882_01/server.112/e41573/hintsref.htm#PFGRF501

刚刚开始，我进行hash join连接发现如下：

SQL> select /*+use_hash(emp)*/ empno from emp,dept where dept.deptno=emp.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 716400937

-----------------------------------------------------------------------------------

| Id  | Operation         | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

-----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT  |               |    14 |   140 |     1   (0)| 00:00:01 |

|   1 |  NESTED LOOPS     |               |    14 |   140 |     1   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN | IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

|*  3 |   INDEX RANGE SCAN| REVERSE_INDEX |     1 |     3 |     0   (0)| 00:00:01 |

-----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   3 - access("DEPT"."DEPTNO"="EMP"."DEPTNO")

SQL>

我明明指定的是emp做为驱动表然后进行hash join，但是不行，需要指定另个表，但是use_hash不能规定优化器来选择驱动表。

eg：

SQL> select /*+use_hash(emp,dept)*/ empno from emp,dept where dept.deptno=emp.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 2255485930

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("DEPT"."DEPTNO"="EMP"."DEPTNO")

SQL> select /*+use_hash(dept,emp)*/ empno from dept,emp where dept.deptno=emp.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 2255485930

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("DEPT"."DEPTNO"="EMP"."DEPTNO")

SQL>

我们可以选择使用ordered或是leading来指定optimizer选择哪个表为驱动表。

note：

The LEADING hint instructs the optimizer to use the specified set of tables as the prefix in the execution plan. This hint is more versatile than the ORDERED hint.

The LEADING hint is ignored if the tables specified cannot be joined first in the order specified because of dependencies in the join graph. If you specify two or more conflicting LEADING hints, then all of them are ignored. If you specify the ORDERED hint, it overrides all LEADING hints.

The ORDERED hint instructs Oracle to join tables in the order in which they appear in the FROM clause. Oracle recommends that you use the LEADING hint, which is more versatile than the ORDERED hint.

When you omit the ORDERED hint from a SQL statement requiring a join, the optimizer chooses the order in which to join the tables. You might want to use the ORDERED hint to specify a join order if you know something that the optimizer does not know about the number of rows selected from each table. Such information lets you choose an inner and outer table better than the optimizer could.

eg：

SQL> select /*+leading(emp) use_hash(dept,emp)*/ empno from dept ,emp where dept.deptno=emp.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 929644576

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("DEPT"."DEPTNO"="EMP"."DEPTNO")

SQL> select /*+leading(dept) use_hash(dept,emp)*/ empno from dept ,emp where dept.deptno=emp.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 2255485930

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("DEPT"."DEPTNO"="EMP"."DEPTNO")

SQL> 
SQL> select /*+ordered use_hash(emp,dept)*/ empno from emp,dept where emp.deptno=dept.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 929644576

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("EMP"."DEPTNO"="DEPT"."DEPTNO")

SQL> select /*+ordered use_hash(emp,dept)*/ empno from dept,emp  where emp.deptno=dept.deptno;

Execution Plan

----------------------------------------------------------

Plan hash value: 2255485930

----------------------------------------------------------------------------------

| Id  | Operation        | Name          | Rows  | Bytes | Cost (%CPU)| Time     |

----------------------------------------------------------------------------------

|   0 | SELECT STATEMENT |               |    14 |   140 |     2   (0)| 00:00:01 |

|*  1 |  HASH JOIN       |               |    14 |   140 |     2   (0)| 00:00:01 |

|   2 |   INDEX FULL SCAN| REVERSE_INDEX |     4 |    12 |     1   (0)| 00:00:01 |

|   3 |   INDEX FULL SCAN| IND_EMP       |    14 |    98 |     1   (0)| 00:00:01 |

----------------------------------------------------------------------------------

Predicate Information (identified by operation id):

---------------------------------------------------

   1 - access("EMP"."DEPTNO"="DEPT"."DEPTNO")

SQL>

oracle hints的更多相关文章

  1. Oracle Hints详解

    在向大家详细介绍Oracle Hints之前,首先让大家了解下Oracle Hints是什么,然后全面介绍Oracle Hints,希望对大家有用.基于代价的优化器是很聪明的,在绝大多数情况下它会选择 ...

  2. Oracle Hints具体解释

    在向大家具体介绍Oracle Hints之前,首先让大家了解下Oracle Hints是什么,然后全面介绍Oracle Hints,希望对大家实用.基于代价的优化器是非常聪明的,在绝大多数情况下它会选 ...

  3. 普及下Oracle hints语法

    普及下Oracle hints的语法:{DELETE|INSERT|SELECT|UPDATE} /*+ hint [text] [hint[text]]... */ 1.hint只能出现在诸如sel ...

  4. Oracle Hints详细解释

    特别介绍给大家Oracle Hints之前,让我们知道下Oracle Hints什么,然后好Oracle Hints,我们希望实际.基于成本的优化器是很聪明,在大多数情况下,将选择正确的优化,减少DB ...

  5. 常用oracle hints

    在SQL语句优化过程中,经常会用到hint, 以下是在SQL优化过程中常见Oracle中"HINT"的30个用法 1. /*+ALL_ROWS*/ 表明对语句块选择基于开销的优化方 ...

  6. 详解Oracle hints PQ_DISTRIBUTE

    PQ_DISTRIBUTE是并行的hints中稍微复杂一点的一个 下面就这个hints做以下说明: 1.使用格式 /+ PQ_DISTRIBUTE(tablespec outer_distributi ...

  7. Oracle数据库基础知识

    oracle数据库plsql developer   目录(?)[-] 一     SQL基础知识 创建删除数据库 创建删除修改表 添加修改删除列 oracle cascade用法 添加删除约束主键外 ...

  8. Oracle提示大全

    Hint概述 基于代价的优化器是很聪明的,在绝大多数情况下它会选择正确的优化器,减轻了DBA的负担.但有时它也聪明反被聪明误,选择了很差的执行计划,使某个语句的执行变得奇慢无比. 此时就需要DBA进行 ...

  9. SQL调优 - Hints指定索引 解决慢查询案例

    背景 每当交易高峰时期,可能会暴露一些平时无法发现的问题,机遇和挑战并存.下面聊聊最近解决的一个案例,因为执行计划走错导致慢查询,进而引发应用线程阻塞.线程池爆满,最后应用功能瘫痪.如何标本兼治的解决 ...

随机推荐

  1. js日期格式，日期对象

    以对象为基准去使用方法, 围绕Date对象 var a = new Date() 返回当前的时间对象,可以使用内置的日期对象的方法 a.getFullYear(), a.getMonth(), a.g ...

  2. 网上流行的add(2)(3)(4)

    网上有很多其他的各样的算法.其实这题就可以用javascript属性arguments.callee来实现,代码如下: function add(x){ var result=0; return fu ...

  3. LINUX 压缩目录成一个压缩文件

    #!/bin/bash file =$(date +%y%m%d%H%M)logfile=/home/目录名/backup/file.log echo "------"$(date ...

  4. 开发中遇到的angularJs的小问题

    1.在使用自定义指令后如果需要将指令内部的数据传给外层controller需要设置scope属性,此时注意,如果指令内传出的数据在某种情况下需要清空,如传出一个选中元素的数组,点击清空按钮则清空选中这 ...

  5. jQuery监听键盘事件及相关操作使用

    一.首先需要知道的是: 1.keydown() keydown事件会在键盘按下时触发. 2.keyup() keyup事件会在按键释放时触发,也就是你按下键盘起来后的事件 3.keypress() k ...

  6. JS实现继承多态

    //类对象构造模版,无new访问,类似静态访问 var Class = { create: function () { return function () { //initialize初始化 //a ...

  7. 为何要fork()两次来避免产生僵尸进程??

    最近安装书上说的,开始搞多进程了..看到了一个好帖子,学习学习 http://blog.sina.com.cn/s/blog_9f1496990100y420.html 首先我们要明白,为什么要避免僵 ...

  8. webStorm中的混乱代码格式化

    Mac上    command + alt + l windows上 control + alt + l

  9. Java: 实现顺序表和单链表的快速排序

    快速排序 快速排序原理 快速排序(Quick Sort)的基本思想是,通过一趟排序将待排记录分割成独立的两部分,其中一部分记录的关键字均比另一部分记录的关键字小,则可对这两部分记录继续进行排序,以达到 ...

  10. webserver<1>

    1. 实现基础的信号处理 sigaction使用前一定内存清零 2. 实现基础的进程模型 wait 等待子进程结束 #include <stdio.h> #include <unis ...