SAP SLT Protocol Table Index

[timo_bruentjen_ewe_de]

Hello,

Im facing big latency times on accessing a SLT created Protocol Table in the source system. the index of the created protocol table is not optimized for the system.

Is there a way to influence the protocol table creation process, like optimizing the index to get better read times?

Best regards

[Andrey_M · Accepted solution]

As "protocal table", I guess, you mean logging table.

Actually the logging table is very good optimized to use one in SLT scope. SAP don't suggest any additionally optimization recommendation for that.

[lumirion · Accepted solution]

Sorry, but what is the evidence for your statement? We are facing the same issue and an additional index on the logging/protocol table helped out.

[Andrey_M · Accepted solution]

My statement based on experience of thousands customers who replicate tables with terabyte data.

We are working together with DB experts who suggest us different ways to optimize tables and indices. If you have a problem with latency I can suggest you to open ticket and describe your findings. Team will carefully investigate it and provide a patch if you finding will be approved by our DB experts.