Does deleting obsolete tables and transaction codes affect the system performance?

[Former Member]

Hi Everyone,

I am conducting a research about the performance impact on deleting obsolete tables and transactions codes.

Will there be really an impact on the system performance when I delete obsolete tables and T-codes?

For example,

I plan to delete 50 tables and 100 transaction codes will the system increase in speed and performance?

Thanks,
Francis.

[matt]

No affect on performance. Why would it?

However, if you contract a third party to perform an upgrade, for example, they may well base their price on the number of custom objects on your system, so removal of obsolete objects is a good idea.

[Former Member]

Hi Matthew,

     I just thought that if freeing some memory up for the system will give it a little boost on the speed and performance. Just like when cleaning up a computer's memory/internal storage.

Thank you for your response this will be a great help on my research.

Regards,
Francis

[matt]

In the case of SAP unused objects aren't in memory (except with HANA as your db), there's vast quantities of disk space and processing power (and memory with HANA) available. Removing a few MB out of a TB database if it makes a difference at all (smaller number of files = faster handling) it'll be so negligible as to be unnoticeable. Not the place to concentrate if you want a faster system.

If you really have performance problem - get a faster server. One client I had switched to linux so the savings on software licensing for a proprietary unix went on buying (leasing!) a bigger box.

[Former Member]

Hi Matthew,

So even though we create millions of tables, transactions and programs even on a low memory system it will still not affect the system's performance?

Thank you for your response

Regards,
Francis

[matt]

Why should it? They're on disk.

I could (via some kind of HD to serial port interface) attach a few full 4TB drives to my old 16K ZX81. It wouldn't run any slower.

[Jelena_Perfiljeva]

Francis, I'm also confused why do you believe that something that is not even executed would be in memory?

When unneeded objects are removed, it is never done for the performance reasons, but just to maintain a "clean" system. There are more benefits in not having to check "what the heck do we have this for?" during an upgrade than in having 0.00000000000000001% runtime improvement.

If you are looking for the justification to remove unneeded objects, I believe this question has already been asked on SCN a few times, you might want to search.

[Former Member]

Hi Jelena and Matthew,

     I have now a clear understanding regarding this. That there will be no effect on the system performance no matter how many objects you have since it will not be in the memory and it will be in a different storage.

     I will focus more on program optimization to make the system faster.

     Thank you for your responses this is a great help for my research.

Noted, I'll search deeper next time before asking questions. Thank you

Regards,
Francis.
    

[Jelena_Perfiljeva]

Number of transaction codes has nothing to do with performance. But it's good to delete the redundant ones anyway.

The dictionary definition of the tables have no effect on performance. The data in those tables I guess can hypothetically have some effect (consuming disk space and such) but most likely marginal. Still it's better to delete what's not used.

Good point about the upgrades. Even if you DIY it's better to get rid of all the unneeded stuff to avoid warnings coming up and such. During the upgrade the schedule is tight usually, so the less you need to check the better.

[Former Member]

You can feel free to delete the obsolete tables or transaction codes which you have created and are not using now without worrying about system..

Since you are working on performance check.. Code optimizing is better way to make a program run faster.. Use SAP Trace to track the time your program took and you can see which query is taking time and you can do necessary optimization to speed it up..

The Number of System objects wont effect your performance of a program or a particular transaction