Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle and small tables

Re: Oracle and small tables

From: Joel Garry <>
Date: 13 Mar 2006 14:25:22 -0800
Message-ID: <>

>And I have one more question. Because I found that tables with about
>10,000 records are small tables :) I am testing Oracle, and I had to
>make some database to test it. I have 9 tables - 5 have more than
>1,000,000 records and 2 have about 100,000 records. I would like to
>know if it is good for tests that I don't have, for example every
>table which contains more than 1,000,000 records. In my opinion it is
>better to have diverse tables in database. Am I right?
>Thanks a lot for every answear!

It really depends. I don't know what you mean by diverse tables. Generally, it is best to properly design with normalization, so the answer ought to be dependent on your requirements.

People put a lot of work into tpc tests, for example, and does that mean it is a useful measure for any arbitrary app? No, it doesn't. It barely is a good measure of the same tpc test between platforms.

So the basic question becomes, what kind of database are you talking about? Data Warehouse, Decision Support, Data Acquisition and OLTP have very different requirements and use, and mixtures of them make it even more complicated. Then you often add on bizarro front ends.

In the Oracle world, 5 million-row tables is not very big at all - a db I'm looking at just now has over 30, some with tens of millions of rows, and I consider it fairly small - export takes less than 20 minutes. Perhaps more important are locking and concurrency issues. If all you test is one session doing select * from some_table, toy databases will often win out.


-- is bogus.
"This DAT ripped apart directories on our Oracle servers. Check your
databases before production starts!! Someone should be sued over this."
Received on Mon Mar 13 2006 - 16:25:22 CST

Original text of this message