Re: Sybase/Oracle table size limitation / Largest production database

smsi (smsi_at_texas.net) wrote:

: Is there anyone out there that has implemented a Sybase/Oracle table within a
: database instance that is greater than 1 million rows? How large was it
: and what platform were you using?
 

: I have been told by knowledgable DBAs that both Oracle and Sybase performance
: goes down the toilet after about 1 million rows due to the index
: mechanism. This may apply to insert, delete, update and/or read.
 

: Has anyone done benchmarks to this effect, i.e. response time for each
: type of operation vs. size vs. number of database clients?
 

: Thanks
: Robert Lesieur
: Southwestern Bell

1> sp_spaceused sec_price
2>

 name                 rows        reserved   data       index_size unused     
 -------------------- ----------- ---------- ---------- ---------- ---------- 
 sec_price            22608460    3.4796e+06 2.21446e+0 1.26502e+0 124 KB     

We use the above table in applications everyday. We continue to get sub-second response using the clustered index. Nightly jobs used to add 30k rows/night (before we went on a diet. 8-)

The database is on a Sparc 1000 running solaris 2.4 with Sybase 4.9.2.

Hint: If you have a table this big, put it in a database of its own... Ask me why I know... :-/

Dave Harper
State Street Global Advisors Received on Thu Nov 02 1995 - 00:00:00 CET