Re: triggers/stored procedures/SYSTEM command

> > The performance you are noticing is suprising to me. I have used the > SYSTEM command from within stored procedures without any performance > problems. > Have you thrown in any timing checks to make sure it is really the SYSTEM > call that is the problem and not the actual UNIX program that is being > run? > -Toby Denbow > tdenbow@mathworks.com That would be a trick, given that the SPL sets the time for the entire SPL at the same time. So: (if there were indeed a sleep) LET dtm = CURRENT YEAR TO SECOND; SLEEP 45; LET dtm2 = CURRENT YEAR TO SECOND; Will yield the same time for dtm as dtm2 in my experience. A cow-orker tested out 'system' in a situation where he needed OLTP style transactions. He found that it consistently took about .5 seconds to invoke the system command each time. In his case that wasn't acceptable. Errr, don't ask me how he timed it.... :-) cheers j. _____________________________________________________________________________ Jack Parker - Hewlett Packard, DMD/IS Boise, Idaho, USA jparker@boi.hp.com Currently on loan to PLD/PE _____________________________________________________________________________ If anything can go wrong, fix it. To hell with Murphy. _____________________________________________________________________________ Any opinions expressed herein are my own and not those of my employers. _____________________________________________________________________________