cancel
Showing results for 
Search instead for 
Did you mean: 

Table Splitting

Former Member
0 Kudos

Dear Experts,

if we have a big table having size 300 with 2 billion record in it.

How many splits are recommended to be done on this table?

Is there any max number for table splitting?

Read somewhere that recommendation is to have table split in such a way that it should not contain more than 10 million records per split.

Required expert inputs here.

Best Regards

Sachin Bhatt

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks Amit/PremSukh,

I have gone through the blog that you referred, However, statements in the blogs are ambigous:

"First of all, you have to calculate in how many packages you are going to split your "trouble table". My advice is to split a table up to packages of 5 GB max. In this case, my 500 GB VBOX table should split into 10 packages."

so it says to split 500 GB table in 5 GB packages. However, if you split it into 10 packages your each split will 50 GB & not 5 GB. That means we have to make 100 splits of this table to get 5 GB split.


so it doesnt really help.


Also I want some recommendation from SAP documents rather than random blogs. Have you ever gone through any such SAP documents where table splitting has been discussed in detail to this extent.


Best Regards

Sachin Bhatt



BorisZarske
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Sachin,

The 10 million lines per table are listed in the for migrations to SAP HANA, Some of the recommendations are also valid for general migrations (not only for migrations to SAP HANA), they are listed in the normal system copy guide, such as in section "Preparing the Table Split":


"We recommend that you perform a test run to identify the tables with the longest runtime, as not always the largest tables require the longest runtime. To get statistical data about runtimes, use Migtime during the export and import (for more information, see SAP Note 784118)."


In the best practice guide, you can also find an example ("5. Appendix: Example - Optimizing the Runtime for Migration of SAP BW Test System") - even if not everything will apply for all databases, it might be a good start point for performing your own test run to optimize all involved parameter for your boundary conditions.


Best regards,

Boris

0 Kudos


Hello Sachin,

This topic is well discussed in the forums. Please refer to the below links for more details

http://sap10.blogspot.de/2013/01/heterogeneous-system-copy-export-table.htmlhttp://
https://scn.sap.com/thread/334951

Hope this helps!

Amit