cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Data File size considerably reduced after Unicode Conversion

Former Member
0 Kudos
239

Hello Experts

I have just performed a CUUC (Upgrade along with unicode conversion) from R/3 4.7 to ECC 6.0 EHP5. The data size that i earlier had was close to 463 GB (MSSQL MDF, LDF Files), after the data export to be converted to unicode the size was 45 GB (10% of actual data size, i feel this is normal after heterogeneous system copy), but after the import again the DATA file size is only 247 GB, is this normal ? or have i lost some data ? For ex, I tried checking tables like MSEG and the number of entries have reduced from 15,678,790 to 15,290,545.

Could you kindly let me know if there is a way to check from Basis perspective if i have not lost any data ? I have followed all the procedures as per SAP Standards.

Waiting for your quick reply.

Best Regards

Pritish

Accepted Solutions (0)

Answers (3)

Answers (3)

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Pritish,

did you compare SAP ECC 6.0 (Non-Unicode) with SAP ECC 6.0 (Unicode) ?

did you also check the numbers which can be found in the TOC files ?

Best regards,

Nils Buerckel

Former Member
0 Kudos

Hi Pratish,

Table entries before export should be either equal or more after the import.As long as export and import have been

completed successfully its ok. However since you have a question in mind that table entries after the import are less when

compared before i would consider redoing the export and import again.

Its always a good idea to get the table entries for around 100-150 tables before export and then compare them post import.

Regards,

Ershad Ahmed.

nicholas_chang
Active Contributor
0 Kudos

Hi,

Is normal that you Database will getting smaller after import, as reorganization will perform during export/import. Also, if you are using MSSQL server 2008, there's a data compression feature enabled.

refer to:

Note 1488135 - Database compression for SQL Server

Note 1505884 - R3load: compression for table / index

Hope it helps,

Cheers,

Nicholas Chang

Former Member
0 Kudos

Hi Nicholas

Data is compressed during the new R3load procedure is understood, but why number of table entries have reduced is something which is still a question to me (in some cases increased as well) ? For example

Source Target

STPO 415,725 412,150

STKO 126,710 126,141

PLAF 74,671 78,336

MDKP 193,487 192,747

MDPB 55,329 63,557

Any suggestions or ideas ?

Best Regards

Pritish