RE: Optcompind

Bill, If you have upgraded to a newer version recently, setting it to '0' ensures that your join methods remain same as in the earlier version. Other wise you have to set OPTCOMPIND, based on the nature of your data /table schema/queries. OPTCOMPIND influences the query plan in this way: If set to 2 , the query plan is selected strictly on the basis of cost. If set to 1, for Dirty Read/Committed Read/Cursor Stability Isolation levels it acts as if set to '2' and for Repeatable Read acts as if set to '0'. (This is pretty logical , as in RR Isolation level , a hash join would lock the table badly.) If set to 0, Whenever Indexes are available , Index scans are preferred over table scans. (Hence in a join you would see Nested Loops instead of hash joins.) Hope that helps ' raju ---------- From: Weaver, Bill [SMTP:bweaver@fscorp.com] Sent: Thursday, September 07, 2000 5:26 PM To: 'informix-list@iiug.org' Subject: Optcompind I still consistently see the suggestion on the list that optcompind should be set to 0 rather than 2. I've run with 2 for quite a long time and I saw a suggestion today that said to change it to 2 rather than 0. Is that something that was "fixed" in a later version (the question was in regards to IDS 2000)? In other words, are there versions that you should never set it to 2 on but should always use 0? Or is this just another case of try it and see what works best for you type of thing? _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.