Re: Why the query buffers are more than row size?

From: <asprusch_at_my-dejanews.com>
Date: Fri, 24 Jul 1998 06:25:41 GMT
Message-ID: <6p99d6$n9g$1@nnrp1.dejanews.com>

Not only full table scans needs to fetch blocks. There are index range scans too. Try tkprof with explain option. Each step of execution will list with the number of rows returned by the step, i believe.

Hope this will help,
Andreas Prusch

In article <35B7B249.9E944B20_at_cisco.com>, kkethine_at_cisco.com wrote:
> All my SQL scripts, when monitored using SQL_TRACE, are querying
> huge amount of buffers than the actual rows fetched.
>
> Why is it happening? There are no FULL scans.
>
> The below is an example of fetching a single row.
>
> call count cpu elapsed disk query
> current rows
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> Parse 1 0.00 0.00 0 0
> 0 0
> Execute 2 0.03 0.04 0 0
> 1 0
> Fetch 1 20.59 57.66 8806 152983
> 150 1
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> total 4 20.62 57.70 8806 152983
> 151 1
>
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Fri Jul 24 1998 - 01:25:41 CDT