Hi there,
we have a problem at a customer site that relates to the SBO-COMMON "SEVT" Table.
The Customer has been loading data into their SBO System by various means (DTW, DIAPI, DI Server) for the last coupole of months. It's a very high volume of data. the Customer is on 882 PL6.
Now, their SEVT Table now contains 123 MILLION records.
The table is taking 34GB of physical disk space and every time this table is hit by SAP, it's causing a 3-5 second slowdown for everything.
I urgently need some help on the following two queries:
1. How do I stop this table from eve being written to? I have followed the Notes referenced in SAP Note 1411696 and as per that note the issue is still present. So basically it would seem that no matter what you do, if you use the DIAPI/DI Server to put records into the SAP system, you get SEVT records written. But there must be a way to turn this off and if not, we urgently need one.
2. How can we manage these records? As far as I can tell, assuming the customer is not actually interested in these events, there can be do harm from a truncation of this table (and yes I know this is not "allowed" by SAP, it's up to me to get them to agree to this as a special case). But I would love to know if anyone else has had a similar problem, and how they ended up resolving it.
Many thanks,
Stephen