Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Ben Meijs Ctac on Oct 3 at 2:24 AM Hi,
Besides the useful tips and hints already put forward (design of program, clearing internal tables when not needed anymore, limiting het number of columns of internal tables, sizing of the user sessions), a simple tip is to limit the use of Global Data in your program. Keep everything local in your procedures except the data that you really need to keep global. All the temporary global internal tables that are used are then not forgotten to be cleared.
Met vriendelijke groeten / kind regards,
Ben Meijs
| | | ---------------Original Message---------------
From: Terry Barker
Sent: Thursday, October 02, 2014 2:46 PM
Subject: Maximum Rows Of An Internal Table
I think this is going to depend on the per-user memory allocation limit set on the system. If the goal is to extract massive amounts of data for a one-time event, it is better to get your DBA to extract the data at the DBMS level. (We had to do this once to satisfy a request from an auditor--although I still wonder what they actually did with tens of millions of records.) |
| Reply to this email to post your response. __.____._ |   _.____.__ |
