I have an internal table which has more than 2,00,000 lines. This table is formed by the data in the application and this table is going to grow. Right now i am not facing any performance issue or load issue. But i would like to know if there is a limit on having data in internal tables and will effect performance in long run
Technically no set limit but performance wise it will depend on the data, the doc design, the usage and the hardware. A table with few unique values and few fields will handle better than a highly distinct one with a large amount of fields. If the rest of the data model is well designed (more of the star schema type) this is good for the performance as well.
Anyway, the 200.000 rows (or is it 2 million? ) is not bad and as long as you have some decent hardware backing you up you should be fine for quite some time unless you're adding a very large number of rows in every iteration.
