Re: Fw: 50M records each year.. how to handle

[Raj Shekhar]

 <sudhir543-nimavat <at> yahoo.com> writes:

> But app will need to create a new table every year and alter merge
> table definition..

Right.  ALTER table on a merge table is a fast operation.  A MERGE
table need not maintain an index of its own because it uses the
indexes of the individual tables. As a result, MERGE table collections
are very fast to create or remap.


> However I doubt that merge table would give a decent performance for
> Select operaton..

I cannot comment on the above statement without seeing your table
indexes and your select queries.  If you use optimal indexes, you will
have fast selects.