Re: Performance problem with big table!
Posted in 1999
Topics: Performance & Tuning, Clustering, Grid & MACH11, Versions, Editions & End-of-Life
Check your OPTCOMPIND, this should be 0. If it is not 0, this will have impact on SQL selects being scanned sequentially. Rgds "Art S. Kagel" wrote: > Have you updated statistics according to the recommendations in the > Performance Guide? Or get my dostats.ec utility which implements this > protocol for generating and maintaining useful database statistics and data > distribution information for the optimizer. Dostats is part of the package > utils2_ak which is available for download from the IIUG Software Repository. > > Art S. Kagel > > "Kim, Hyung Soo" wrote: > > > > Do you using clusterd index? > > > > Xavier Mertens <xavier@euro.net>ÀÌ(°¡) ¾Æ·¡ ¸Þ½ÃÁö¸¦ > > news:Pine.GSO.4.21.9912110107250.9821-100000@caolila¿¡ °Ô½ÃÇÏ¿´½À´Ï´Ù. > > > Hi *, > > > > > > We run an IDS 7.31 on a SUN Enterprise 450. > > > The database contains some tables with no more than 1000000 rows. > > > > > > Today we added a new table with 10.000.000 rows and 3 indexes. (the table > > has > > > less than 10 fields) > > > > > > A simple query like "select * from table where label = x" take more than > > 10"!!! > > > (and label is a unique index) > > > > > > Any idea? > > > > > > X > > > > > > -- > > > Xavier Mertens, . . EuroNet Internet > > > Network Operation Center . * a subsidiary of France Telecom > > > XM3-RIPE XM1-6BONE . > > >