<font size=2 face="sans-serif">Hi WUGgers,</font>
<br>
<br><font size=2 face="sans-serif">This might sound like a stupid question
(apologies in advance), but I keep reading (on SCN, and in Practical Workflow
for SAP) that the event trace is bad for performance (as noted/discussed
below). My question would be - <b>why</b> is it bad for performance?
</font>
<br>
<br><font size=2 face="sans-serif">You certainly introduce a large number
of writes to the event log table, but I wouldn't think that it would really
have an on performance unless you were to also read from the table on a
regular basis. As long as the space consideration of the event log
table is dealt with by running the job to clear it down every once in a
while, then it seems feasible to leave it running.</font>
<br>
<br><font size=2 face="sans-serif">Best Regards,<br>
James Johnson<br>
<br>
E-mail:JJohnson@uk.ibm.com<br>
Mobile: 07908715224 or 07920870270</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Rick Bakker <rbakker@gmail.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"SAP Workflow
Users' Group" <sap-wug@mit.edu>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">06/03/2014 22:55</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: Workflow
Event Trace Leave On or Turn Off</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sap-wug-bounces@mit.edu</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3>Hi Eddie,</font>
<br>
<br><font size=3>Thanks for sharing your (formidable) experience. Could
you tell us more about the situations where this brought the system down?</font>
<br><font size=3>Luckily I haven't encountered such a problem yet but I
sure would like to know about it. </font>
<br>
<br><font size=3>I have found the event trace to be extremely useful in
many cases. In the most trivial case it's good for convincing a user that
yes, they did indeed press the Cancel button.</font>
<br>
<br><font size=3>regards</font>
<br><font size=3>Rick Bakker</font>
<br>
<br><font size=3><br>
</font>
<br><font size=3>On Thu, Mar 6, 2014 at 11:33 PM, Morris, Eddie <</font><a href=mailto:eddie.morris@sap.com target=_blank><font size=3 color=blue><u>eddie.morris@sap.com</u></font></a><font size=3>>
wrote:</font>
<br><font size=2 color=#004080 face="Calibri">Hi Rick,</font>
<p><font size=2 color=#004080 face="Calibri"> </font>
<p><font size=2 color=#004080 face="Calibri">Speaking from experience I
have seen this take systems down on quite a few occasions so it can go
horribly wrong. If you have someone who can monitor it and delete trace
data when needed then I guess it is workable. Also use the trace restrictions
when switching it on so only monitor a select number of events.</font>
<p><font size=2 color=#004080 face="Calibri"> </font>
<p><font size=2 color=#004080 face="Calibri">Also with note 1905199 a syslog
entry (SM21) is written when an event linkage is deactivated so this can
be used to check when the event linkage deactivation occurs. Then use the
event trace to get specific information about the deactivation itself.</font>
<p><font size=2 color=#004080 face="Calibri"> </font>
<p><font size=2 color=#004080 face="Calibri">Regards,</font>
<p><font size=2 color=#004080 face="Calibri">Eddie</font>
<p><font size=2 color=#004080 face="Calibri"> </font>
<p><font size=2 face="Tahoma"><b>From:</b> </font><a href="mailto:sap-wug-bounces@mit.edu" target=_blank><font size=2 color=blue face="Tahoma"><u>sap-wug-bounces@mit.edu</u></font></a><font size=2 face="Tahoma">
[mailto:</font><a href="mailto:sap-wug-bounces@mit.edu" target=_blank><font size=2 color=blue face="Tahoma"><u>sap-wug-bounces@mit.edu</u></font></a><font size=2 face="Tahoma">]
<b>On Behalf Of </b>Rick Bakker<b><br>
Sent:</b> 05 March 2014 22:17<b><br>
To:</b> SAP Workflow Users' Group<b><br>
Subject:</b> Re: Workflow Event Trace Leave On or Turn Off</font>
<p><font size=3> </font>
<p><font size=3>Hi David,</font>
<p><font size=3> </font>
<p><font size=3>I like to leave the event trace turned on. I have found
this to be the case at most sites. Also, most workflow people I have worked
with agree with this approach. The overhead is minuscule compared to the
information it adds.</font>
<p><font size=3> </font>
<p><font size=3>regards</font>
<p><font size=3>Rick Bakker</font>
<p><font size=3> </font>
<p><font size=3>On Thu, Mar 6, 2014 at 3:29 AM, Edward Diehl <</font><a href=mailto:edwarddiehl@hotmail.com target=_blank><font size=3 color=blue><u>edwarddiehl@hotmail.com</u></font></a><font size=3>>
wrote:</font>
<p><font size=4 face="Garamond">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.</font><font size=3><br>
<br>
</font><font size=2 face="Tahoma"><b><br>
Ed Diehl</b></font><font size=3 face="Tahoma"><i><br>
"Success consists of going from failure to failure without loss of
enthusiasm."</i> <br>
<br>
</font>
<div align=center>
<hr></div>
<p><font size=3>To: </font><a href="mailto:sap-wug@mit.edu" target=_blank><font size=3 color=blue><u>sap-wug@mit.edu</u></font></a><font size=3><br>
From: </font><a href=mailto:davidcooper06@icloud.com target=_blank><font size=3 color=blue><u>davidcooper06@icloud.com</u></font></a><font size=3><br>
Subject: Workflow Event Trace Leave On or Turn Off<br>
Date: Wed, 5 Mar 2014 06:55:50 +0000</font>
<p><font size=3> </font>
<p><font size=3>Hi All,</font>
<p><font size=3> </font>
<p><font size=3>The following is more a discussion item!</font>
<p><font size=3> </font>
<p><font size=3>I have read in various texts and heard from several workflow
administrators that it is recommended to turn the workflow trace off in
production.</font>
<p><font size=3> </font>
<p><font size=3>Reasons:</font>
<p><font size=3>1) The trace adds an overhead to the application and database
servers, and</font>
<p><font size=3>2) The trace fills up the event table(s) with data that
is not needed over time.</font>
<p><font size=3> </font>
<p><font size=3>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.</font>
<p><tt><font size=3>Kind Regards</font></tt>
<br><tt><font size=3>David Cooper</font></tt>
<br><tt><font size=3>Linked-In: </font></tt><a href="http://www.linkedin.com/pub/david-cooper/47/616/36a" target=_blank><tt><font size=3 color=blue><u>http://www.linkedin.com/pub/david-cooper/47/616/36a</u></font></tt></a>
<br><tt><font size=3> </font></tt>
<p><font size=3> </font>
<p><font size=3>_______________________________________________ SAP-WUG
mailing list </font><a href="mailto:SAP-WUG@mit.edu" target=_blank><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3>
</font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a>
<p><font size=3><br>
_______________________________________________<br>
SAP-WUG mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:SAP-WUG@mit.edu" target=_blank><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a>
<p><font size=3> </font>
<br><font size=3><br>
_______________________________________________<br>
SAP-WUG mailing list</font><font size=3 color=blue><u><br>
</u></font><a href="mailto:SAP-WUG@mit.edu"><font size=3 color=blue><u>SAP-WUG@mit.edu</u></font></a><font size=3 color=blue><u><br>
</u></font><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank><font size=3 color=blue><u>http://mailman.mit.edu/mailman/listinfo/sap-wug</u></font></a><font size=3><br>
</font>
<br><tt><font size=2>_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<br><font size=2 face="sans-serif"><br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>