Problems with 7.12 optimizer

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. Contact your mail administrator for information about upgrading your reader to a version that supports MIME. ------ =_NextPart_000_01BB4955.EB29BED0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit We are having a problem with the 7.12 optimizer. We have a select statement that looks like the following. select field1 from tab1,tab2 wheretab2.field2 matches "*STRING*" and tab1.key_ = tab2.key_ tab1 has index i1tab1 on tab1.key_ tab2 has index i1tab2 on tab2.key_ and index i2tab2 on tab2.field2 what is happening is that the optimizer is chosing to join the tables and do a sequental scan for field2. Which turns into a very costly query (3-4 min). What I expect to happen is tab2 would be filtered by field2 and then joined with table tab1 after. I have seen this problem before under 7.XX online and was able to fix it by setting OPTCOMPIND=0. This allowed the optimizer the ability to find the correct path and return the query quickly. The problem is how do I tell Standard Engine this? Any ideas??? Russ.... __________________________________________ Russell P. Kahler russell@oncontact.com (414)375-6540 W67 N250A Evergreen Blvd. Cedarburg, Wi 53012 ___________________________________________ ------ =_NextPart_000_01BB4955.EB29BED0--