Re: SERVEROUTPUT Status

Syltrem wrote:

> Hello again!
>
> The way I use it now suits me very well, and I was only asking "why not ever
> use it?" because I thought maybe there was a big performance issue with it,
> or something else that I should be aware of and would mean that I must stay
> away from dbms_output in production.
>
> The way our system works, messages are output to the log file and sometimes
> also in an Oracle table. If the job bombs out someone is emailed with the
> log file and he's got all the details in there (thanks to dbms_output).
> Important jobs are also logged into an Oracle table for later reference.
>
> Thanks for all your answers everyone !

I say never because the investment of a few seconds into converting it into an insert gives more value. Same as I say don't ever use a unique index, use a unique constraint. Or never use dictionary managed tablespaces.

If there is something better that can be implemented in a few seconds it is better to use it. I didn't mean to imply there was something terrible about the package or its use. It just isn't as good as a simple alternative.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)