SWPM table splitting - deciding number of splits for a table ?

[danielsapbasis]

Hi Experts,

How to decide the numbers of splits for a table in SWPM source export preparation.

what factors to be considered.

* Is SWPM database export running the table splitting and package splitting internally?

if so, don't we need to run the table splitting separately?

Please answer and clarify.

Thanks in advance

[dasistdochscheisse · Accepted solution]

IMO, the most important factor for table splitting is the needed time for the export. When one table uses let's say 4 hours to be exported and all other packages need 2 hours, it makes sense to split this table in 2 packages so you don't have to wait till the import starts. I guess you make a HANA or unicode conversion and when it comes to the productive system it's all about minimizing downtime. It wasn't unusal to make several test exports with a copy of the prod. system to get the last bit of optimization for a really important system (1hour downtime meant several hundreds of thousand cashflow loss).

If time is no problem, there is no need to split the tables at all. But expext to have a very long runtime (could be days) if you don't split the biggest tables.

[rsnit]

Hi Daniel,

UMG_R3LOAD_RUNTIME_PREDICTION gives a good prediction for tablesplitting e.g. packages for tables etc.

here an example

br

[JamesZ]

Please check:

https://help.sap.com/docs/SLTOOLSET/ae1552407b9846a1997cc04b9fce521e/934c66b213344f87a4b606f803722de...

we must explicitly run table split, and normally it only makes to run table split for big table.

[danielsapbasis]

Hi Zhang,

I dont see an answer for deciding the number of splits to table.

<nr_of_splits>

Please let me know the deciding factors.

Thanks in advance

[JamesZ]

Yes, we need to self decide, basically start from big table