Re: Triggers or application code? Which is more efficient?

For a data load process (if it is a lot of data), my personal preference is to use SQL*Loader to slam all the data into staging tables as quickly as possible and then use stored procedures/packages to manipulate the data as needed. However, if you are already using some developed dataload software, I would determine whether or not the normal system users would need to be restricted to these same business rules when modifying data (unless the users only access the database in a read-only fashion). If they do need to follow these rules, I would use the triggers (unless the system is such a heavily updated system that I think extra constraints would hinder performance). Hope this outside perspective helps.

Jeff S

<ahcarson_at_bglasscity.cnet> wrote in message news:3783513a_at_news.glasscity.net...
>
> Triggers or application code? Which is more efficient?
>
> What are the costs/benefits of triggers vs. adding code to
> dataload software to support more complex integrity checks?
>
> Any thoughts on which is more effecient?
>
> Howard (remove 'a' 'b' 'c' to email)
Received on Thu Jul 08 1999 - 21:51:40 CDT