Re: My first large table

• Use automatic segment management for this table with uniform extent size big enough (you need 9i for that, and you might need a new tablespace also).
• Explore the possibility of partitioning it. For example, if the data will be queried usually by date, one partition by month or year. You could then archive the old partition when they're getting old.
• Create indices on the columns which will be used frequently in the WHERE clauses of the SQL statements. Indices usually don't need to be reorg'ed unless a significant portion of the rows were recently deleted.
• Make sure indices and table do not use the same disk (especially the disk controller). ...

Daniel

> Currently have a small database with no table having more than 50000
> rows.
> Now we have a requirement to load large amounts of data into a table
> which will be held for 3 months, resulting in several million rows.
> The data will be loaded using sqlldr and thereafter queried for adhoc
> report purposes only.
>
> Just want to know, what are the basic things I need to do in setting
> up this table to ensure decent performance.
>
> Do I need to reorganize the table indexes on regular basis to retain
> performance? If so how? As you can tell I'm quite new at this!
>
> Thanks in advance,
> JL
Received on Fri Jul 18 2003 - 14:05:05 CDT