costs something to maintain the index, too. (Time to look for a book on SQL
that talks about such things...)
- Original Message -
From: Jacque Scott
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 29, 2004 6:28 PM
Subject: Re: More Left Join problems
Jacque Scott
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Thursday, January 29, 2004 2:18 PM
Subject: Re: More Left Join problems
Thanks for your time. I didn't think of formatting the query. Here is
the query in a more readable format. I have also taken out most of the
columns in the SEL
are testing
aren't available for the where clause to use.
- Original Message -
From: Jacque Scott
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Thursday, January 29, 2004 2:18 PM
Subject: Re: More Left Join problems
Thanks for your time. I didn't think of format
e the examples
as short as possible. I probably saw and ignored your earlier
question for that reason; I usually just skip messages where it
would take too long to decipher the question--I'd assume that other
people do the same.
HTH
Bill
> Date: Thu, 29 Jan 2004 08:03:25 -0800
> From
gnored your earlier
question for that reason; I usually just skip messages where it
would take too long to decipher the question--I'd assume that other
people do the same.
HTH
Bill
> Date: Thu, 29 Jan 2004 08:03:25 -0800
> From: "Jacque Scott" <[EMAIL PROTECTED]>
> To
I had posted a message earlier this week about my 'Left Join' taking too
long to run. This seems to be happening on all of my queries that have
a 'Left Join'. Does anyone have any suggestions on why this would
happen?
Here is one query which took 45.72 sec to run:
SELECT Products.NSIPartNum
