SQL vs. VBA
 

I was wondering if a trigger created via sql in Oracle would perform faster
than the equivalent vba function in excel that is uploading to Oracle?

Either way I am running a program to upload data into Oracle using VBA. I
was thinking of making some of the Excel VBA tasks the database's tasks
through a trigger, but in order to do that I have to do the "work aorund" for
Oracle so I can work on the same table. I experimented with a small dataset
and when using triggers, the program time seemed to triple if not more. Any
thoughts? Thank you.

Brent

SQL vs. VBA
 

To be honest, the only thought that crosses my mind is:

Try it and find out.

MH

"Brent" wrote in message
...
I was wondering if a trigger created via sql in Oracle would perform faster
than the equivalent vba function in excel that is uploading to Oracle?

Either way I am running a program to upload data into Oracle using VBA. I
was thinking of making some of the Excel VBA tasks the database's tasks
through a trigger, but in order to do that I have to do the "work aorund"
for
Oracle so I can work on the same table. I experimented with a small
dataset
and when using triggers, the program time seemed to triple if not more.
Any
thoughts? Thank you.

Brent

SQL vs. VBA
 

Depends on what the trigger does, and whether it's implementing a "business
rule" which would apply to all data going into the table, or just the data
being loaded from your application.


Tim




"Brent" wrote in message
...
I was wondering if a trigger created via sql in Oracle would perform faster
than the equivalent vba function in excel that is uploading to Oracle?

Either way I am running a program to upload data into Oracle using VBA. I
was thinking of making some of the Excel VBA tasks the database's tasks
through a trigger, but in order to do that I have to do the "work aorund"
for
Oracle so I can work on the same table. I experimented with a small
dataset
and when using triggers, the program time seemed to triple if not more.
Any
thoughts? Thank you.

Brent