Poorly written, implemented, designed and tested triggers - will have a high impact on your UV system.
Hopefully, you have down a full-scale (real world-like) production-like test in your UAT environment prior to implementing them. If you have done this and tested real world scenarios like file, group & record-lock contention - the stuff you could possibly get in your environment - you'd probably ok. :) As "we" don't know your application, your existing system load, existing file types or configuration or what your trigger does...we can only speculate wildly on the impact. :) As others have commented, the overhead can be substantial. So it is a trade-off of functionality your desire versus the actual performance hit. A delicate balance here, that only you can decide through thorough and rigorous testing. The more reading and writing your triggers do - the greater the impact (and the more locks they will hold). Clearly, if your triggers are updating, you do need be very concerned about performance. If you have no updating, there is less to worry about. However, just reading records can also set database record locks, as well. Regards, David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Roosa Sent: Wednesday, 8 October 2008 2:22 PM 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/
