Data size Catagory.

[Former Member]

Hi,

In SE11, in Technical Settings, there is a field for DATA size catagory.

what significance this field has?

i searched forums, most of the replies were it is just an indication and it can be overshot etc. Basically they were telling it was simillar to "occurs" in ABAP reports.. (my interpretation)

I have a report which has performance issue and it is accesing standard function modules to evaluate the output.. but still it is taking long time to execute and hence giving the time_out error.

After running SE30 on the report, i found 97% of the time was taken by database queries which reside within standard SAP programs. So, i could not make any programming modifications, but all of the database tables which consume more time have overshot their respective data size catagory atlease by 2-3 times.

Is it the reason report is giving performance issue? should i consider all the tables mentioned for archiving? is the data size catagory number a standard which should be maintained in order for system to run smoothly?

[Former Member]

Hi,

Size category is the max. no. of data records a table can hold. If the records in the table are more than the size category it throws dump. So it can be further enhanced by Basis.

[Former Member]

No, it doesnt work that way.

[Former Member]

Hi Sumalatha,

R u sure it is so.

[Former Member]

Hi

Size category defines how much memory that porticular field can hold.If the field length is less than size category it will throw dump.Its better to adjust the size category to maximum,but extra space is wasted.

[Former Member]

>

> Hi 
> 
> Size category defines how much memory that porticular field can hold.If the field length is less than size category it will throw dump.Its better to adjust the size category to maximum,but extra space is wasted.

Please press F1 on the field before answereing.

Rob

[Former Member]

Hi,

I think there won't be a major problem because of SIZE CATEGORY, it just defines the Max No of records a table can hold.just check out some performance improvement tips.

it would have been better if you would have pasted the screen shot of your report(FM calling coding part).

Regards,

Mukesh

[Former Member]

Hi Chinmay,

Kindly go through this link,

http://help.sap.com/saphelp_nw70/helpdata/EN/c9/02561b6dc4ef46a21b68c1fc178560/content.htm

Hope it helps you

Regrds

Mansi

[ThomasZloch]

Expected size of the table, also determines the size of additional extents once the size has been reached, no dump whatsoever.

I've heard that the code inspector (SCI) uses the size category to analyse potential performance problems of open SQL statements.

Thomas

[Former Member]

Hi,

Data size category determines the number of records a table can hold.

An initial extent(memory) is reserved for every table which will be created in the database,but,we need to give size category to provide enough memory for the records that would be created at future point once the initial extent gets filled up.

If suppose the initial extent is 8 bytes and size category mentioned is 12 bytes,once this initial extent gets filled up ,next 12 bytes will be alloted and once this 12 bytes gets filled ,another 12 bytes will be allotted,this continues.

So, if you are sure that you will be entering few records,then choose size category accordingly,while creating table ,depending on the fields of the table and datatypes of the fields,size category values gets changed.

[Former Member]

The Size category describes the probable space requirement of the table in the database.

It varies from (0-4) .Each category is assigned a certain fixed memory size in the database, which depends on the database system used.

When a table is created, initial space i,e Initial Extent) is reserved in the database. If more space is required for data entries, additional memory will be added depending on the selected size category.

[Former Member]

This message was moderated.

[Former Member]

Hi chinmay kulkarni ,

Size category mainly describes about the size(number of records) that a table occupies.

There are different categories.Based on the number of records we require then we go for size categories.

For example,

A company requires to maintain 5,000 records then we go for category 0 like that we choose the size categories.

There is an initial fixed size for every table and there after it allocates the size based on the user selected size category.

Thanks

Kiran

[gaursri]

Hi Chinmay,

I read the question. I think the major concern is the database usage, and ,not the size category .As you wanted to minimize the database usage.It may be possible that size category is increasing the usage.As the size category you have mentioned will eventually leads to the number of records you can create in the Dictionary.If during the process the size category is increasing definately the database performance will be in red.That is 97% as you stated.

If during the process there is no added entry or adjustment in the database table then this is not the reason.

The database performance also depends on Indexes.So I would suggest that check on Indexes Primary or Secondary.I hope once we analyze the index usage we can minimize the error.

[Former Member]

Hi,

I faced a similar situation some time and got it resolved after the basis has increased the size limit of the table.

[Former Member]

Hi,

Size category in the table will indicate that how many buffer rows allocated to that particular table. After this will overflow it will allocate the same amount of buffer rows again.

[Former Member]

Hi,

http://help.sap.com/saphelp_nw70/helpdata/EN/c9/02561b6dc4ef46a21b68c1fc178560/content.htm

Hope this link helps you

Regards,

Rajani

[Former Member]

Hello Chinmay,

Try reading the F1 help provided; and you'll be clear of the size category

" The size category determines the probable space requirement for a table

in the database.

<< Cut and paste from http://www.erpgenie.com/forum/viewtopic.php?f=1&t=12970 removed >>

Regarding the performance issue..

Please make sure that you have provided all the key fields in the se3lect query and also, make sure that the fields mentioned in the select query are exactly in the same order as they appear in the Data base table.

Also, make sure that you have not used Select--Endselect.

Ensure that joins are used properly

Also try to avoid Order By in the select statement. Instead, try to read the data into internal table and then Sort the table.

Theses are some of the tips to improve the performance of the select statement. In order to avaoid short dump, try to execute the program in back ground; and if you are sure that the performance issue is because of size category, you may increase it as per requirement.

Regards,

Shiny

Edited by: Rob Burbank on Feb 9, 2009 9:25 AM

[Former Member]

Size category

Allows you to specify estimated space requirement for the table.

<< Cut and paste from http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ead2446011d189700000e8322d00/frameset.htm removed >>

shravani boddu - Welcome to SDN. We appreciate your effort to contribute, but before posting, please read the rules of engagement. Cutting and pasting answers without attributing the source is frowned upon here.

Edited by: Rob Burbank on Feb 9, 2009 9:51 AM

[Former Member]

don't copy&paste from copy Righted material

Edited by: Vijay Babu Dudla on Feb 12, 2009 6:49 AM

[Former Member]

<< Cut and paste without attribution from http://www.sappages.com/abap-dictionary-2/ removed >>

Edited by: Rob Burbank on Feb 13, 2009 9:08 AM

[Former Member]

Enough is enough.

Rob