Re: My first large table

The number of rows don't mean much and even if you grow to 20 Million rows, it probably (depends on total table size) would perform well with the basic type stuff covered like (as 1 example) no full table scans in explain plan output.

But, I think a more significant number is the total size of the table in number of bytes, not rows.

For example, 2 tables with the same number of rows could have significantly different total sizes. If you have a lot of large columns with data, then the total size of the table in Megabytes will be much higher than a table with just a few small columns.

-- 
"John Leslie" <johnleslie_at_madasafish.com> wrote in message
news:4412dd31.0307180425.760beccc_at_posting.google.com...


> 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