Frank van Bortel wrote:
> DA Morgan wrote:
>
>>Frank van Bortel wrote:
>>
>>
>>>Jeremy wrote:
>>>
>>>
>>>>In article <d7i5hn$45o$1_at_news5.zwoll1.ov.home.nl>, Frank van Bortel
>>>>says...
>>>>
>>>>
>>>>
>>>>>>When you say "submit a job" can you tell me what you mean - are you
>>>>>>referring to dbms_job ?
>>>>>>
>>>>>>
>>>>>
>>>>>Exactly - write a packaged procedure to do the updates, and call it
>>>>>using dbms_job
>>>>>
>>>>
>>>>
>>>>Thanks Frank - one final question on this... is it better to use the
>>>>DBMS_JOB approach or to use autonomous transations?
>>>>
>>>>cheers!
>>>>
>>>
>>>
>>>Eh? Two different beasts. Jobs are like scripts - you start them,
>>>forget about them, and -when finished- look at the results.
>>>Autonomous transactions are transactions, started as part of another
>>>transaction, that have their own commit/rollback point, independent
>>>of the main transaction - autonomous. Useful for auditing.
>>>
>>>The beauty of a job is that you just fire-and-forget: there's instant
>>>response back to the user: we started a job for you with ID #276, you
>>>can check on it's status <a href="whereever your links are"> by
>>>clicking here</a>
>>
>>
>>Of course if you want to see the progress you can build calls to
>>DBMS_APPLICATION_INFO.SET_SESSION_LONGOPS in the called proc.
>
>
> But then it would be like MS Windows again, wouldn't it?
Depends on how you implemented getting the information: But yes.
--
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Tue May 31 2005 - 15:15:32 CDT
