Re: WHERE 1=2 with performance nightmares
- From: "Dennis Landi" <nada@xxxxxxxx>
- Date: Thu, 2 Aug 2007 08:06:41 +0530
"Kim Madsen" <kbm@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:46b0f077@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
Sounds like a where clause added by an api or middleware to get the field
definitions but not any records.
Is "1" and "2" supposed to be the respective columns in that queried table?
If so, then "1" may well equal "2" at any given time for any given table...
If both columns are integer-based IDs, then this is likely. It could even
explain the percieved performance hit.
It looks like Ralf Jansen has good advice on how to disable the "SET FMTONLY
ON" behaviour.
-d
.
- Follow-Ups:
- Re: WHERE 1=2 with performance nightmares
- From: Steve Troxell
- Re: WHERE 1=2 with performance nightmares
- From: Michael Fritz
- Re: WHERE 1=2 with performance nightmares
- References:
- WHERE 1=2 with performance nightmares
- From: Sarah
- Re: WHERE 1=2 with performance nightmares
- From: Kim Madsen
- WHERE 1=2 with performance nightmares
- Prev by Date: Re: Extremely long build times
- Next by Date: Re: Great day in the "Developers Days in Espaņol".
- Previous by thread: Re: WHERE 1=2 with performance nightmares
- Next by thread: Re: WHERE 1=2 with performance nightmares
- Index(es):
Relevant Pages
|