That's why I asked how do you plan to send the output? 1. you could mail it 2. you could stream it to PC using utl_tcp 3. you could spool to file using utl_file 4. You could write a pipelined function instead of procedure to send periodic output to screen. That's why I asked what version? Raj On 8/25/05, Jeffrey Beckstrom <JBECKSTROM@xxxxxxxxx> wrote: > > That's what we were thinking of. The problem with sql*plus is that > procedure has to end for output to get to screen. Then how do you reinvoke > the procedure again. DBMS_JOB won't send output to a client PC. > > >>> rjamya <rjamya@xxxxxxxxx> 8/25/05 7:54:17 AM >>> > What version? How do you want to send output? You could easily do this > using sqlplus or dbms_job. A procedure and a mechanism to otput is all you > need. > > raj > > On 8/25/05, Jeffrey Beckstrom <JBECKSTROM@xxxxxxxxx> wrote: > > > > Our developers have a requirement to query a table and send the output > > to a PC every N minutes. Developers don't know Perl so looking at some > > alternatives. I would hate to do it in Sql*plus since would have to start > > sql*plus, connect, run procedure, exit and repeat. That would be a lot of > > connecting. > > Any other suggestions. > > Jeffrey Beckstrom > > Database Administrator > > Greater Cleveland Regional Transit Authority > > 1240 W. 6th Street > > Cleveland, Ohio 44113 > > > > > > -- > ------------------------------ > select standard_disclaimer from company_requirements where category = > 'MANDATORY'; > -- ------------------------------ select standard_disclaimer from company_requirements where category = 'MANDATORY';