RE: Using SQL to check for duplicate records

Not quite a view, but very similar, and lightning fast, was this:
WITH 
  TEMPTABLE (IPROD) AS 
    (SELECT IPROD 
       FROM IIM 
       GROUP BY IPROD 
       HAVING COUNT(*)>1) 
SELECT TEMPTABLE.IPROD, RRN(A) 
  FROM TEMPTABLE, IIM A 
  WHERE TEMPTABLE.IPROD = A.IPROD

Rob Berendt
-- 
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)




"Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/06/2004 11:34 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: Using SQL to check for duplicate records






Have you tried this?
Create View IPRODDups as 
    SELECT IPROD FROM IIM group by IPROD 
    Having count(*) > 1
Select IPROD,RRN(IIM) A join IPRODDups B 
    on A.IPROD = B.IPROD order by A.IPROD

I've discovered that creating views can dramatically reduce the execution
time of SQL statements in some circumstances. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
Maybe my problem is how I am joining back.  Any suggestions?
<clip>
_______________________________________________
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.