Re: SELECT DISTINCT(columname) and TEMP dbs

}>From ilist@rmy.emory.edu Thu Jun 5 04:22:28 1997 }>Received: from rmy.rmy.emory.edu by hobbes.dbintellect.com via ESMTP (950413.SGI.8.6.12/930416.SGI.AUTO) }> for <settler@dbintellect.com> id EAA13566; Thu, 5 Jun 1997 04:21:32 -0600 }>Received: (from ilist@localhost) by rmy.rmy.emory.edu (8.7.1/8.7.1) id EAA13503 for informix-list-out; Thu, 5 Jun 1997 04:00:01 -0400 (EDT) }>From: blefever@xs4all.nl (Bob Lefevere) }>Message-Id: <33966150.2639365@news.xs4all.nl> }>Subject: Re: SELECT DISTINCT(columname) and TEMP dbs }>Date: Thu, 05 Jun 1997 07:06:06 GMT }>Reply-To: blefever@xs4all.nl (Bob Lefevere) }>Organization: XS4ALL, networking for the masses }>Sender: informix-list-owner@rmy.emory.edu }>To: informix-list@rmy.emory.edu }>X-Informix-List-Id: <news.38782> }> }>On 16 May 1997 10:43:13 -0400, settler@emory.mathcs.emory.edu (Jeff }>Craig) wrote: }> }>>}> I am trying to execute a simple query such as: }>>}> SELECT DISTINCT(columnname) }>>}> FROM ANYTABLE }> }>Did you check if you're running out of locks ? If so, you could do: }>begin work; }>lock ANYTABLE in exclusive mode; }><query etc.> }>commit work; }> I'm not out of locks, but thanks for the suggestion. I think the problem is that I do not set either PSORT_NPROCS or PDQPRIORITY prior to running the statement, so the sorts are serial. It is a large table, but the performance is abysmal. I will be testing this further when I get a dedicated test environment set up. ------------------------------------------------------------------- Jeff Craig | dbINTELLECT Technologies, Inc. Senior Consultant | Golden, CO | (303) 275-6954 ext. 8008 | email: settler@dbintellect.com | fax: (303) 275-2134 -------------------------------------------------------------------