Date: Fri, 9 Jul 2004 12:58:30 -0400
Reply-To: "Wainwright, Andrea" <andrea.wainwright@CAPITALONE.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: "Wainwright, Andrea" <andrea.wainwright@CAPITALONE.COM>
Subject: Re: Why would you ever merge without a by variable
Content-Type: text/plain
Actually, I had one file with say 1 MM records, and was merging in data from
another file that had more than 1 MM records but only wanted records that
were from the first file.
So I expected 1 MM and got 1 MM since it stopped once it was done with the
smaller file. There just wasn't anything in the log to clue me in to why
the results were wrong.
I am going to have to see about having MERGENOBY=WARN added to our autoexec,
and if not I will copy their autoexec, add it, and use my own version.
-----Original Message-----
From: Tim Berryhill [mailto:tim@AARTWOLF.COM]
Sent: Sunday, July 04, 2004 7:43 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Why would you ever merge without a by variable
My current site is adding MERGENOBY=WARN to our preferred options. That
said, I have merged without a BY when one of the datasets had only 1
observation and I wanted to smear it across the other dataset. I suppose
one could also code
IF _N_ EQ 1 THEN SET SINGLE_OBS_SET;
SET MANY_OB_SET;
By the way, congratulations for checking the log. It can be quite
informative to expect 100+100=100 (tidy merge) and see 100+100=110
(unmatched keys). Tim "Wainwright, Andrea"
<andrea.wainwright@CAPITALONE.COM> wrote in message
news:D5170EA5CC08D5119F160002A52CBD1F25AD3FF6@kdcnt4mbx06.kdc.capitalone.com
...
<snip>
> Anyway, I am really just ranting, but I really would love a real world
> example where you merge without a BY variable.
**************************************************************************
The information transmitted herewith is sensitive information intended only
for use by the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.
| 
