Date: Mon, 19 Jun 2006 11:34:02 -0400
Reply-To: "Fehd, Ronald J. (CDC/CCHIS/NCHM)" <rjf2@CDC.GOV>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Fehd, Ronald J. (CDC/CCHIS/NCHM)" <rjf2@CDC.GOV>
Subject: Re: What does nodup do in proc sort?
Content-Type: text/plain; charset="us-ascii"
OT response re uniqueness
PROC SQL; select dictinct ID ...
Ron Fehd the SQL maven CDC Atlanta GA USA RJF2 at cdc dot gov
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org] On Behalf Of Arthur Tabachneck
> Sent: Sunday, June 18, 2006 9:53 PM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: What does nodup do in proc sort?
> While I have often suggested that one typically wants to use
> nodupkey in proc sort, a recent poster had a problem that
> sounded like nodup might have produced the desired result.
> However, in testing what I thought would occur, I got results
> that I wasn't expecting. The test data and sample program follow:
> data have;
> input id Dose score;
> 1 100 10
> 1 100 22
> 1 200 15
> 1 100 30
> 2 100 5
> 2 100 30
> 2 200 10
> 1 100 10
> proc sort data=have out=want nodup;
> by id;
> Given the above, how many records should result in file 'want'?
> If your answer is 8, please explain why that result occurs.