Workflow Event Trace Leave On or Turn Off

[Edward Diehl]

It's not whether or not the trace is running, it's how often you delete "old" entries and reorg it.  Having said that, we have stopped using it to test for duplicate events and now check for duplicate workflows in a check function.

Ed Diehl
"Success consists of going from failure to failure without loss of enthusiasm." 



To: sap-wug at mit.edu
From: davidcooper06 at icloud.com
Subject: Workflow Event Trace Leave On or Turn Off
Date: Wed, 5 Mar 2014 06:55:50 +0000

Hi All,
The following is more a discussion item!
I have read in various texts and heard from several workflow administrators that it is recommended to turn the workflow trace off in production.
Reasons:1) The trace adds an overhead to the application and database servers, and2) The trace fills up the event table(s) with data that is not needed over time.
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.Kind Regards
David Cooper
Linked-In: http://www.linkedin.com/pub/david-cooper/47/616/36a


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140305/ab82be5e/attachment.htm