<?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 &amp;quot;OUT OF RESOURCES &amp;quot; Disk Full But plenty of disk space in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363349#M86026</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to merge two dataset using PROC SQL&lt;/P&gt;&lt;P&gt;First dataset is only 400MB and second one is 170MB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if I merge two, I got messages&amp;nbsp;"OUT OF RESOURCES " Disk Full&lt;/P&gt;&lt;P&gt;Currently I got 300GB of local disk space and both datasets are not in work library and of course I the merged dataset is&amp;nbsp;&lt;/P&gt;&lt;P&gt;to be create in other library that is located in local disk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is this happens???&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone help?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 09:29:41 GMT</pubDate>
    <dc:creator>jkim197</dc:creator>
    <dc:date>2017-06-01T09:29:41Z</dc:date>
    <item>
      <title>"OUT OF RESOURCES " Disk Full But plenty of disk space</title>
      <link>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363349#M86026</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to merge two dataset using PROC SQL&lt;/P&gt;&lt;P&gt;First dataset is only 400MB and second one is 170MB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if I merge two, I got messages&amp;nbsp;"OUT OF RESOURCES " Disk Full&lt;/P&gt;&lt;P&gt;Currently I got 300GB of local disk space and both datasets are not in work library and of course I the merged dataset is&amp;nbsp;&lt;/P&gt;&lt;P&gt;to be create in other library that is located in local disk.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is this happens???&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone help?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 09:29:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363349#M86026</guid>
      <dc:creator>jkim197</dc:creator>
      <dc:date>2017-06-01T09:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: "OUT OF RESOURCES " Disk Full But plenty of disk space</title>
      <link>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363353#M86029</link>
      <description>&lt;P&gt;SQL can be more resource hungry as it does internal sorts/merges etc. &amp;nbsp;Can't really tell much from the bit of information you posted. &amp;nbsp;Try doing a datastep merge, or debugging the SQL.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do also note that resources could refer to physical memory, not just hard disc space. &amp;nbsp;You might need to extend the amount of ram allocated to SAS, or install more. &amp;nbsp;Again, its still hard to say as no information.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 09:44:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363353#M86029</guid>
      <dc:creator>RW9</dc:creator>
      <dc:date>2017-06-01T09:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: "OUT OF RESOURCES " Disk Full But plenty of disk space</title>
      <link>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363367#M86030</link>
      <description>&lt;P&gt;Please show the SQL code (and the whole log from the step). An accidental unconditional cartesian join of two datsets like this can easily result in a multi-terabyte output.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And keep in mind that a SQL join will use lots of space in your work (and/or UTILLOC, which is by default in WORK) anyway, no matter where the source and result tables are located. So if you do not have at least the size of both tables combined available in your work, the SQL will unvariably fail.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My personal preference is to always do joins in datasteps, unless I really &lt;U&gt;do&lt;/U&gt; need to build a cartesian join, which is easier done in SQL.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 11:19:17 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/quot-OUT-OF-RESOURCES-quot-Disk-Full-But-plenty-of-disk-space/m-p/363367#M86030</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-06-01T11:19:17Z</dc:date>
    </item>
  </channel>
</rss>

