Hi, We are working with our newly aquired 8GB Sun Solaris Sparc system. We figured once the DATA_CACHE was populated that most of our SELECT statements would scream... as we are only working with 10GB of data... Solaris shows that disk writes are being performed during our SELECT statements, even when it appears all the data is in MaxDB cache. I can only suspect this is Temporary Table activity? Is there any way to hint to MaxDB to use RAM for Temporary Tables? Any tricks to suggest? This is a read-only database that will be used for data analysis... any and all tips on getting MaxDB to use that RAM to best advantage are appreciated. Thank you. Stephen Gutknecht -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
