>Profile(sex,entpc,laccess) and profile(sex,entpc,faccess) >Would appear to be called for. Obviousdly you will wish to analyze the >schema, and even more obviously you will do all this in test first. >If sex is a column that does not have many values (one would think no >more than 8 or so) then you can make this a compressed index degree 1, >if entpc also has very few values compressing it degree 2 might be >helpful (though I'd be sceptical).
Thanx a lot for your suggestions Niall. i hope the indexes on sex & entpc in profile table is not necessary. so there are some unwanted indexes to be dropped. "On the contrary, the performance by index scan will decrease because Oracle must translate the <prefix, suffix> part in corresponding key" Found the above lines in a metalink doc. about index compression. I don't know how far it will affect my performance.Need to test it. Thanks and Regards, Jp. -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Prem Khanna J INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
