topic Re: diff b/w pooled table and cluster tables in Application Development and Automation Discussions

diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:02:23 GMT

i want exact diff b/w these.and some examples

thanks

Re: diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:09:24 GMT

You can find the answer by searching this forum.

Click 'search forum'

Enter 'difference pooled cluster table'.

Read through the replies.

Regards,

Nick

Re: diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:12:04 GMT

Hi Prasad,

Check these posts

Regards,

Satish

Re: diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:21:09 GMT

Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored.

Cluster tables contain continuous text, for example, documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least parts of the keys must agree. Several cluster tables are stored in one corresponding table on the database.

Re: diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:30:52 GMT

<b>cluster tables :</b>

>maintains prinary key reationship.

>these are less no of cluster table which had large no of

records

>cluster tables can not buffered.

Example : Cluster table :BSEG

<b>pooled tables :</b>

> doesnt maintain any primary key relationship

>these are more no of pooled table which had less no of

records

>Pooled tables are buffered

Example : Pool table : MDTC

Regards,

Maha

Re: diff b/w pooled table and cluster tables

Former Member — Wed, 28 Nov 2007 17:39:46 GMT

Nick,

People will never search the forum as long as there are people like those above who want to grab some points by answering these kind of questions instead of advising people to search the forum.

Regards

Aneesh.

Re: diff b/w pooled table and cluster tables

Former Member — Thu, 29 Nov 2007 05:11:40 GMT

Pooled table

Pooled tables can be used to store control data (e.g. screen sequences,

program parameters or temporary data). Several pooled tables can be

combined to form a table pool. The table pool corresponds to a physical

table on the database in which all the records of the allocated pooled

tables are stored.

Cluster table

Cluster tables contain continuous text, for example documentation.

Several cluster tables can be combined to form a table cluster. Several

logical lines of different tables are combined to form a physical record

in this table category. This permits object-by-object storage or

object-by-object access. In order to combine tables in clusters, at

least part of the keys must agree. Several cluster tables are stored in

one corresponding table on the database.

Pool Tables (match codes, look up tables)

Should be accessed via primary key or

Should be buffered (SE11->Display Table->technical settings)

No secondary indexes

Select * is Ok because all columns retrieved anyway

Cluster Tables (BSEG,BSEC)

Should be accessed via primary key - very fast retrieval otherwise very slow

No secondary indexes

Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required.

Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported

Can not be buffered

IV. Buffered Tables (includes both Transparent & Pool Tables)

While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.

pooled - many to one

cluster table - many to one

poolled and cluster table both are logical tables

A001,A004,A005,A006,A007,A009,A010,A012,A015,A016,A017,A018,A019,A021,A022,

AUAA,AUAB,AUAO,AUAS,AUAT,AUAV,AUAW,AUAY,BSEC,BSED,BSEG,BSES,BSET,CDPOS

Refer link: http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm

Re: diff b/w pooled table and cluster tables

former_member188829 — Thu, 29 Nov 2007 07:02:33 GMT

HI,

Check this thread..

Check these links...

http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f083446011d189700000e8322d00/content.htm