One gotcha is that once a trigger is on there, you can't easily change/extend it unless your system has a downtime period in which everyone is logged out. For this reason on 24x7 sites I use a master trigger that can call subtriggers, held as a list in a parameter file. This means that a new subtrigger can be inserted, old subtriggers removed etc without having to log everyone out. Yes, it means an extra read and yes it is an imperfect solution in an imperfect world..
And of course remember you are running under transactional constraints when using triggers. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mike Roosa > Sent: 08 October 2008 04:22 > To: [email protected] > Subject: [U2] Universe Triggers > > We are getting ready to implement triggers on a universe > system running under Windows Server 2003. I created a > trigger and tested it out and it appears to do exactly what > we need. My question is are there any gotchas or issues we > should be concerned about with triggers? Are there any > performance issues that anyone has seen related to triggers? > > Thanks, > Mike Roosa > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
