<html><body><div>Hi All,</div><div><br></div><div>The following is more a discussion item!</div><div><br></div><div>I have read in various texts and heard from several workflow administrators that it is recommended to turn the workflow trace off in production.</div><div><br></div><div>Reasons:</div><div>1) The trace adds an overhead to the application and database servers, and</div><div>2) The trace fills up the event table(s) with data that is not needed over time.</div><div><br></div><div>My argument for leaving the trace running, is more for diagnostic reasons when problems occur in production. It becomes another source for tracking down what happened. Yes the overhead is a given, but I feel this is justified to capture the diagnostic information. As for the database table being filled, implement a deletion strategy which purges the data from the table after a period of say 3 ,6, 9, or 12 months.</div><div><pre style="font-family: 'Helvetica Neue', Helvetica, sans-serif; font-size: 15px; white-space: pre-wrap; word-wrap: break-word;" data-mce-style="font-family: 'Helvetica Neue', Helvetica, sans-serif; font-size: 15px; white-space: pre-wrap; word-wrap: break-word;">Kind Regards
David Cooper
Linked-In: http://www.linkedin.com/pub/david-cooper/47/616/36a
</pre></div></body></html>