Hi,
This may not be a complete answer to your question, this is what i think for the concept of internal tables:
1.You can;t go and access the database table for each & every record(since in most of the cases the production server will be in all together in different geographical location), its a big performance issue.
2.We can not perform complex manipulation on database, as we use to perform it over our internal table.
3.we can associate Internally table to cache memory, and a database table to secondary storage device. so it is suggested to access data from the faster one only.
Hope the above might have cleared your doubt partially.
Regards,
Bharath.
Hi,
data structures are liable to change. Using the data dictionary, a developer can change the internal structure of a line in an internal table without affecting the
persistence of data in DB tables. This allows for more
flexibility and creativity.
It is a good example of separating the interface from the
implementation.
Regards,
Marc
Add a comment