I don't think that it's documented, but you can use the nowarn option in proc sql to get rid of the warning message.
proc sql nowarn;
create table a_comb as
select *
from a1, a2
where a1.msgid = a2.msgid
;
Per @SASKiwi :
please note that the NOWARN option will block all warnings in that step, so if something unexpected happens you may end up blocking other warnings you may prefer to see. Also you are still left with the duplicate columns in the dataset. As long as you are OK with these limitations then no problem!
I don't think that it's documented, but you can use the nowarn option in proc sql to get rid of the warning message.
proc sql nowarn;
create table a_comb as
select *
from a1, a2
where a1.msgid = a2.msgid
;
Per @SASKiwi :
please note that the NOWARN option will block all warnings in that step, so if something unexpected happens you may end up blocking other warnings you may prefer to see. Also you are still left with the duplicate columns in the dataset. As long as you are OK with these limitations then no problem!
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn the difference between classical and Bayesian statistical approaches and see a few PROC examples to perform Bayesian analysis in this video.
Find more tutorials on the SAS Users YouTube channel.