Active Table Logging T000 performance impact

[Former Member]

Hi fellow SAP experts,

I need some advice on system performance impact when switching on Table Logging for T000 - configuration in production please?

We have decided to turn on Table Logging for auditing purposes, only allowing developer config in production following a volume of evidence being supplied.

I need to know how much this activation is going to impact the performance of the companies production environments, how much storage, memory, performance, etc. this function is going to consume and how much of the above consumables I need to cater for now and in the future?

We have a Dual Track environment, BAU want to switch on Table Logging for fix on fail, I want to swich it on for Project deliveries.

Please advise, with referencing if possible?

Thank you kindly

Paul

[Former Member]

Hi Paul,

There has been a constant debate whether table logging affects the System performance, especially in Produciton environment. Please see my comments below :

1) To turn on logging for table T000, you will have to activate the parameter rec/client, with values for one client or all the clients in the System depending on your requirement.

2) This parameter setting will not only log changes to T000, but also for over 28000 tables.

3) But these are customizing tables which usually contain a relatively small amount of data which is changed occasionally.

4) After activating, if you suddenly find performance issues, you can check which tables are causing issues via transaction SCU3.

5) You can go to transaction SE13 and deactivate logging for a table, if you find too many entries for any particular table in SCU3.

So, logging tables doesn't necessarily impact performance. Hope this helps. Please refer to SAP Note-608835 related to this.

Best Regards,

Savitha

[Former Member]

Hi Savitha,

Thank you for these details.  I have advised our SDM and with your confirmation of the T-codes, I can monitor and activate/deactivate the list of tables if we start experiencing issues as a last resort.  I still need to refer to the SAP note too.

Regards

Paul

[Former Member]

Hi,

With logging on config tables as delivered by SAP settings I have not been able to detect any measurable change in performance.  This exercise was performed at 2 different clients, both on ECC6.

Table growth was minimal <100 records per month (for non-transportable config)

Cheers

[Former Member]

To add some inputs to the above,

The parameter rec/client accepts the following values

rec/client  OFF (Default)

rec/client  ALL  (All Clients)

rec/client  100, 200 (Specifying Client Numbers)

Since the table logs are switched on primarily in PRD Servers, you can just maintain the client numbers instead of all which will help you a little bit in overcoming performance issues.

Even we have that activated and we didnt see much of performance issues.

Regards

Rakesh