2007 Jan 24 9:13 AM
Hi,
All the time we use only standard internal tables , in what cases we use sort and hash internal tables.
itab like sorted table of <dbtab> with unique key <col>
eg:
itab like hashed table of <dbtab> with unique key <col>
And i also want the performance tunning steps.
Thanks & Regards,
Sravanthi
2007 Jan 24 9:29 AM
Hi,
For performance tuning steps,you can try transaction ST05 for SQL Performance trace.For ABAP runtime anaysis,try se30.You can execute your program and then check the DB and ABAP access which is greatly beneficial for performance tuning.Further, check "tips and tricks" in se30.You can find some efficient ways of coding.
Regards,
Beejal
**Reward if answer is helpful
Hi,
All the time we use only standard internal tables , in what cases we use sort and hash internal tables.
itab like sorted table of <dbtab> with unique key <col>
eg:
itab like hashed table of <dbtab> with unique key <col>
And i also want the performance tunning steps.
Thanks & Regards,
Sravanthi
2007 Jan 24 9:17 AM
2007 Jan 24 9:19 AM
Sorted Table is most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERTstatement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search
Hashed table is most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
2007 Jan 24 9:29 AM
Hi,
For performance tuning steps,you can try transaction ST05 for SQL Performance trace.For ABAP runtime anaysis,try se30.You can execute your program and then check the DB and ABAP access which is greatly beneficial for performance tuning.Further, check "tips and tricks" in se30.You can find some efficient ways of coding.
Regards,
Beejal
**Reward if answer is helpful
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |