Re: SQL UPDATE using INNER JOIN? -- MIDRANGE-L

Subject: Re: SQL UPDATE using INNER JOIN?
From: Ron Adams <rondadams@xxxxxxxxx>
Date: Mon, 16 Jan 2006 16:03:56 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Is there any difference/advantage to using the EXISTS vs the IN clause? This
is the way I'm currently trying to do it. However, The whole reason for
researching the INNER JOIN was due to this taking a really long time to run.
When the IN clause is used it would appear to be re-querying the table for
every record. You can imagine the overhead and time involved if there are
several hundred thousand records.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL UPDATE using INNER JOIN? , Elvis Budimlic

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.