dilek.ciplak wrote:
> 
> we have sapdb 7.4 running with jboss on win xp server having 1GB RAM.
> 
> as you already know cache_size is the most critical parameter in sapdb
> 
> we decided to give min 128MB, max 512MB for jboss
> 
> set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Xmn128m -Xmx512m set
> JBOSS_HOME=%DIRNAME%\..
> 
> and thougt that it would be enough to separate 160MB to sapdb cache  40000
> (4K each page) totallly
> 
> cache_size=160 MB
> 
> but for tables having more than 300.000  rows our queries do not use the
> index that must certainly be used and do table scans whic means
> the reports running these queries long last

Do you mean: you have indexes you think/are sure that they should be used. But they 
are not used?
Did you see this using EXPLAIN? Did you use UPDATE STATITSICS for the table(s) 
concerned as too old statistics info (now perhaps far away from reality) can result in 
bad search strategies.

Elke
SAP Labs Berlin

> 
> is it possible (logical) to increase the cache_size?
> 
> thanks a lot

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to