Re: SQL issue with EXISTS not "working" -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

There is only 1 occurrence of ITEM in each source file.

On Thu, Oct 23, 2014 at 3:44 PM, Jim It <jim_it@xxxxxxxxxxx> wrote:

Subject: RE: SQL issue with EXISTS not "working"> Date: Thu, 23 Oct 2014

15:31:19 -0400

As long as there are not duplicates within the individual files (non

unique

ITEM) I agree this will do it.

However, if they are unique, I'm curious why the original SQL did not

work

which makes me think his individual files are not unique.

If there were multiple records with the same item# in the source table
which did not exist in already exist in the target table, all of those
records will be written to target table.
This really needs to utilize the Row_Number OLAP function and then select
only the first occurrence of the item#.
Jim

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

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.