Re: How many records in a table can run good ?

South,

    in order for rows to come back fast, when you have a large table, as is your case, you need to have the proper indexes, usually (unless you retrieve a big portion, say more than 25%, of the rows). You need to define your indexes according to the fields used in the WHERE clauses of the SELECT statements (chapter 10 of http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/toc.htm explains this in more details). Secondly, don't partition ("fragment") your table in different databases, as this would greatly reduce performance due to increased network traffic. Instead, think of using "partitions" (read chapter 11 of
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/toc.htm for more details). Let us know if you have some specific questions/issues.

Daniel

> Hi Daniel !
>
> in site tahiti.oracle.com, I had not seen my docs i need, Would you
> please show me clearly. Thanks very much.
>
> Now, my hardware is weak, less, so i had asked that problem.
> With table have 70 milions rows, if the customer access, they loss
> several minutes. So it too long...
>
> So I think I will use method fragment in distributed database, I'll
> separate that table to some table...just I want to know how that ? and
> in every small table Does have many rows ?
>
> Thanks in advance,
>
> South
Received on Wed Jul 23 2003 - 11:08:46 CDT