Performance in table with more than 83 million records

Tuning de Banco, Tuning de SQL, Ferramentas de tuning

Poston Fri, 16 Apr 2010 2:25 pm

I have problem of performance in a table that has more than 83,000,000 of records. I need to make several selects the same being that mostly just data entered later.

Does anyone have any idea to begin to solve the problem?
Location: Nova Hartz - RS

Poston Fri, 16 Apr 2010 2:55 pm

You can use HINTS, create indices according to your parameters, partitioning the table, anyway, there are many exits, but we can only give the best solution when you know where is the bottleneck, take the queries and manages the execution plan of the same, which will show you what the juncoes that \"COST\" to return, if there is FULL TABLE SCAN, etc., which index is being used, start posting execution plans of queries
Location: Recife

Poston Wed, 05 May 2010 5:35 pm

The best way to perform the Tuning is with partitioning by Date Range. In this way, only the partitions for the filter will be accessed. That, combined with Local Indexes, will make everything super fast.

See if your Oracle's Enterprise and if your table has a historical date which is rarely or never updated. EX: date of transaction.

Any doubt, go posting there!
Location: BH - MG

Vitor Leandro

Poston Fri, 14 May 2010 9:13 pm

Friend if it only queries that you are running once, not anything that va always be used.

You can create a smaller table with just the data you need, so you have liberardade and ease to work with the table.

If it is a definitive solution, is what people have already said, there's nowhere to run.
Location: São José dos Campos - SP

O Primeiro passo não vale nada se você não chegar ao final.

Poston Sat, 15 May 2010 2:26 pm

Puts all possible constraints, especially in fields that have indices, to restrict the rows.

And também all the people there spoke.
Location: Seattle, WA, USA

Thomas F. G

Return to DBA Tuning

Who is online

Users browsing this forum: No registered users and 1 guest