Do you know of any white papers specifically on the pro's and con's of DB2 triggers? What are the bad consequences of using DB2 Triggers --- how expensive is it to have the DB2 engine do the data validation for insert / update? One of the positives of using triggers is that the logic does not have to be embedded within each appln using the database, but what are the negatives? If there is only one application that uses the database would you still recommend using "before" triggers for insert / update which basically does data validation or would you want it to be done in the application. If the application and database are not co-located using "before" would triggers result in un-necessary platform hops and therefore would not be recommended? Regards, Rob Arthur ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
