|
Well here's your SQL method and I thinks it's pretty clean: Select KEYFIELD, COUNT(*) >From COLLECTION.TABLE Group by KEYFIELD Having COUNT(*)>1 KEYFIELD can be replaced with multiple fields and I don't mean key in the purest sense, just whatever fields you want to test for uniqueness, even all of them. You can also add an ORDER BY to the end of it if you're so inclined. If you're doing this programmatically, this would become imbedded SQL and you would then deal with the results a record at a time. Hope that helps! > -----Original Message----- > From: Mark Allen > > I need to add duplicate record checking in a file we received from a > switch. (I'll just add it to the CL that already FIXES a > bunch of stuff > in the file anyways) and was wondering what the best (i.e > easy/fast) to > do it would be. I've come up with: > > 3. SQL ??? not done much with it but maybe it could do? NOTICE: This E-mail may contain confidential information. If you are not the addressee or the intended recipient please do not read this E-mail and please immediately delete this e-mail message and any attachments from your workstation or network mail system. If you are the addressee or the intended recipient and you save or print a copy of this E-mail, please place it in an appropriate file, depending on whether confidential information is contained in the message.
As an Amazon Associate we earn from qualifying purchases.
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.