Re: Triggers and External Processes

Chris,

Unless you really need the executable to run immediately the database is updated, you might consider using a trigger to insert a record into a queue table to be processed every x seconds by an Oracle job. This way you avoid overhead on each transaction. You could use an executable running from another machine to scan the queue table and perform tasks if you didn't want to use a job, avioding the additional load on the database server. A queue is sometimes a better alternative since it also allows for your database transactions to go through even if your executable is for some reason unavailable.

HTH, David.

Chris Forlano wrote:

> Is it possible to use a trigger, or a similar mechanism, to spawn
> an external executable on a database server?
>
> For example, say I have an Oracle database running on an
> NT 4.0 server. When a new row is added to a table, can a
> .exe file be run with command line arguments indicating the
> new information added to the database.
>
> I realize that this it is not ideal to have any processes other
> than the database processes running on the server, but, I'd
> like to see what kinds of options we have.
>
> Thanks,
>
> Chris
Received on Mon Jun 07 1999 - 20:55:53 CDT