2007 Jan 18 10:35 AM
Hi..
Can any one tell the exact difference between Clusture & Pooled Table???
2007 Jan 18 10:38 AM
Hi Praveen ,
A major diffrence between the two is in case of cluster tables there must be some relationship ( a common filed) between the tables which form the cluster , but this is not required in case of Pool tables.
Second is cluster table store very large volume of data , where as pooltables are usually creeted by pooling together those table where the volume of data and modification/updates to data is less.
Regards
Arun
Hi..
Can any one tell the exact difference between Clusture & Pooled Table???
2007 Jan 18 10:36 AM
From the F1 help :
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.
Hope this helps,
erwan
2007 Jan 18 10:40 AM
Hi..really thanks for the effort taken for me...what are the contents in cluster table...does it contains all the data's related to customizations done???
2007 Jan 18 10:46 AM
Hi ,
I am not sure whether it contains the data realted to all customizations done , but a very popular example of cluster table is BSEG. Tofind the cluster to which it belongs see the attributes of the table . In this case it is RFBLG
And the volume of data stored in it is really very large.
Regards
Arun
2007 Jan 18 10:38 AM
Hi Praveen ,
A major diffrence between the two is in case of cluster tables there must be some relationship ( a common filed) between the tables which form the cluster , but this is not required in case of Pool tables.
Second is cluster table store very large volume of data , where as pooltables are usually creeted by pooling together those table where the volume of data and modification/updates to data is less.
Regards
Arun
2007 Jan 18 10:48 AM
2007 Jan 18 10:53 AM
hi
II. 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
III. 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
hope this helps
plz reward if helpful.
thankx
2007 Jan 18 10:59 AM
2007 Jan 18 11:04 AM
Hi,
does it contains data related to references between tables????
2007 Jan 18 11:06 AM
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |