topic Re: internal table vs. sql - query in Application Development and Automation Discussions

internal table vs. sql - query

former_member5350 — Tue, 10 Apr 2007 07:53:30 GMT

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

Re: internal table vs. sql - query

Former Member — Tue, 10 Apr 2007 07:55:03 GMT

Hi Clemens,

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

Regards

Mr Kapadia

Re: internal table vs. sql - query

former_member5350 — Tue, 10 Apr 2007 08:00:32 GMT

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

Re: internal table vs. sql - query

Former Member — Tue, 10 Apr 2007 08:00:43 GMT

hi,

Internal table only will be a better choice ...

Regards,

Santosh

Re: internal table vs. sql - query

Former Member — Tue, 10 Apr 2007 08:30:59 GMT

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.

Re: internal table vs. sql - query

Former Member — Tue, 10 Apr 2007 11:11:38 GMT

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.

Re: internal table vs. sql - query

Former Member — Tue, 10 Apr 2007 11:35:28 GMT

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^

Re: internal table vs. sql - query

aris_hidalgo — Wed, 11 Apr 2007 09:24:31 GMT

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...