<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Data step combining data in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424154#M104409</link>
    <description>Yes it is like a union.&lt;BR /&gt;Better depends in your requirements/preferences, but doing it in SQL would get you similar results.</description>
    <pubDate>Sun, 31 Dec 2017 08:10:23 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2017-12-31T08:10:23Z</dc:date>
    <item>
      <title>Data step combining data</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424152#M104407</link>
      <description>&lt;P&gt;I have a basic question:&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data test; set temp1 temp2;run;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Temp1 and temp2 are 2 datasets with similar columns. Can somebody explain what this command is doing. Is it a union of the two datasets. Is there a better proc sql alternative to combine temp1 and temp2.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 31 Dec 2017 07:30:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424152#M104407</guid>
      <dc:creator>Agent1592</dc:creator>
      <dc:date>2017-12-31T07:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: Data step combining data</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424154#M104409</link>
      <description>Yes it is like a union.&lt;BR /&gt;Better depends in your requirements/preferences, but doing it in SQL would get you similar results.</description>
      <pubDate>Sun, 31 Dec 2017 08:10:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424154#M104409</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-12-31T08:10:23Z</dc:date>
    </item>
    <item>
      <title>Re: Data step combining data</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424155#M104410</link>
      <description>&lt;P&gt;This is like a union all in sql. But compare your data step code with the necessary sql code:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc sql;
create table test as
select * from temp1
union all
select * from temp2;
quit;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;and you'll see why it's rarely used when the data step is much more concise. Aside from the fact that the data step has capabilities beyond those of sql.&lt;/P&gt;</description>
      <pubDate>Sun, 31 Dec 2017 08:10:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Data-step-combining-data/m-p/424155#M104410</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-12-31T08:10:53Z</dc:date>
    </item>
  </channel>
</rss>

