Re: SQL with no output

mcstock wrote:

> actually ECHO refers to echoing the SQL statements and SQL*Plus commands
>
> besides some of the other suggestions (depending on how much you want to
> modify the scripts)
>
> 1) nest the statement in a count() statement, i.e.
> select count(<some non-indexes column)) from (
> select ...
> from ...
> )
>
> 2) use the following SQL*Plus commands
> set termout off
> spool some_output_file
> <run commands from a script file>
> set termout on
>
> then do a grep or FIND on the spool file for 'Elapsed'
>
> #1 will be slightly skewed, since the actual rows aren't returned
> #2 will be fairly accurate, except for the latency of screen updates which
> is eliminated by the TERMOUT OFF
>
> -- mcs
>
>
> "Frank" <fbortel_at_nescape.net> wrote in message
> news:bpgm56$2d1$2_at_news3.tilbu1.nb.home.nl...
> | Rick Denoire wrote:
> |
> | > I would like to execute some SQL scripts contained in one file, but I
> | > am actually interested only in the exection time (so I will "set
> | > timing on" in sqlplus).
> | >
> | > How can I avoid getting any output from the scripts other than
> | > execution time? (Using sqlplus, I mean).
> | >
> | > Bye
> | > Rick Denoire
> | >
> | set echo off
> | See SQL*Plus Guide
> |
> | --
> | Regards, Frank van Bortel
> |
>
>

The way I understood the OP's "avoid getting any output from the scripts", echo off would do it.

A column formatting statement of noprint would suppress the output of select statements, but not the linefeeds...

-- 
Regards, Frank van Bortel