Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

internal table vs. sql - query

0 Likes
869

Hi,

i have a project where i need to work with 1, 5 million of datasets from a table. what would be the most effective way to do that assuming i have to loop at the table and compare every row to all the others. Would internal table still be suitable ?

Clemens

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
812

hi,

Internal table only will be a better choice ...

Regards,

Santosh

7 REPLIES 7
Read only

Former Member
0 Likes
812

Hi Clemens,

Could you please elaborate on the requirement ..it would be helpful to suggest.

Regards

Mr Kapadia

Read only

0 Likes
812

Hi,

what i want to do is check wheter a table ( e.g. of debitors ) contains duplicates

( produced by spelling-mistakes etc. ) - as i have to go trough the whole table for that and compare every debitor to all the others i would like to know, wheter this can be done well with an internal table or if i should go for something more efficient.

regards,

clemens

Read only

0 Likes
812

As you will want to edit the name, (to remove spaces), before you sort the list you will need to use an internal table.

If you run out of space you could use an extract dataset, read about FIELD-GROUPS and EXTRACT in the help.

MattG.

Read only

Former Member
0 Likes
813

hi,

Internal table only will be a better choice ...

Regards,

Santosh

Read only

Former Member
0 Likes
812

Hi,

Internal Table is Better choice.

To avoid duplicate entries use the DISTINCT addition in the select query when filling up the internal table.

Use where conditions whenever poosible, read only the required rows or columns into the internal table.

Donot let the internal table become too large: use appropriate Table Type.

->Standard table for multiple access types; use SORT / BINARY SEARCH for mass accesses, and try to SORT only once

->Sorted table if generic key access is the main access type

->Hashed table if single line access with fully specified key is the only access type

Try and use APPEND as much as possible, instead of INSERT.

Make all changes in the internal table and block update into the database table.

Use the TRANSPORTING addition when modifying the internal table.

Hope U did all of them.

  • Award pts for useful answers

regards,

Naveenan.

Read only

Former Member
0 Likes
812

hi

good

i dont think you would face any problem by using the internal table to store any amount iof data.

You can able to use the selct query to select as many number of files..

thanks

mrutyun^

Read only

aris_hidalgo
Contributor
0 Likes
812

Yes, you would have to use an internal table if you would want to compare every record against a given criteria. The only problem is the peformance of your program since you are saying you need to process 1.5 million records.

Hope this helps...

P.S. Please award points if it helps...