Re: SERVEROUTPUT Status

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 !

-- 
Syltrem

OpenVMS 7.3-1 + Oracle 8.1.7.4
http://pages.infinit.net/syltrem (OpenVMS related web site, en français)
---zulu is not in my email address---
"Daniel Morgan" <damorgan_at_x.washington.edu> a écrit dans le message de
news:1076572478.749135_at_yasure...


> Igor Laletin wrote:

>

> > Daniel,

> >

> > Daniel Morgan <damorgan_at_x.washington.edu> wrote

> >

> >>DBMS_OUTPUT does not belong in production code: Ever!

> >

> >

> > I think it's wrong. Like probably the most of the statements with the

> > word 'ever'. DBMS_OUTPUT has two main restrictions: buffer size and

> > line size. They are not a reason not to use it though. Ever! :) If

> > your output fits in, it's the easiest way to go.

>

> Go where? To a monitor in a room that no one ever looks at?

>

> > The output doesn't disappear in nowhere, normally it goes to a

> > logfile. And Syltrem did mention this. I don't know where you get your

> > 'A simple "clear screen" and your record is gone' from.

>

> If the OP did I missed it. But great it is in an operating system file.

> Will anyone read it? Maybe. Can you graph it? No. Can you check deltas

> like last year to this year? No.

>

> >>INSERT INTO <table_name> is overkill?

> >

> >

> > You need:

> > - create table and indexes

> > - code autonomous transaction if there is need for non-transactional

> > output

> > - grant privileges

> > - define, code and monitor purge procedure

> > - provide easy access to the log table (reports, views).

>

> Ok now you got it from five seconds up to 15 or 20.

>

> > All these instead of dbms_output.put_line, which gives the same result

> > and the same persistency.

>

> And is worthless, or nearly so thereafter.

>

> > I'm not saying use dbms_output when ever you need the output from

> > pl/sql. But it's quite appropriate in the Syltrem's situation.

> >

> > Regards,

> > Igor

>

> We must agree to disagree.

>

> -- 

> 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)

>