<?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: vista x64 memory overload in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/vista-x64-memory-overload/m-p/61628#M17501</link>
    <description>sounds like a real reason to ask the experts via Customer Support, or the forms at &lt;A href="http://support.sas.com/techsup/contact/" target="_blank"&gt;http://support.sas.com/techsup/contact/&lt;/A&gt;</description>
    <pubDate>Wed, 05 Aug 2009 12:53:36 GMT</pubDate>
    <dc:creator>Peter_C</dc:creator>
    <dc:date>2009-08-05T12:53:36Z</dc:date>
    <item>
      <title>vista x64 memory overload</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/vista-x64-memory-overload/m-p/61627#M17500</link>
      <description>Hi. I am running sas 9.2 ts1 on vista ultimate x64 with 8gb of ram and 20gb virtual memory allocated. One of my datasets is &amp;gt;9gb. Every time I try to run a procedure (i've tried data step and sort), the memory usage shown on the windows task manager spikes up rapidly to use up all available system memory following which the machine freezes forcing me into a hard reboot. I've tried setting memory allocation as follows:&lt;BR /&gt;
-realmemsize 2G&lt;BR /&gt;
-sortsize 2G&lt;BR /&gt;
-memsize 2G&lt;BR /&gt;
-maxmemquery max&lt;BR /&gt;
sumsize=2G&lt;BR /&gt;
However, this doesn't help either. The confusing part is that on the task manager i don't see any program consuming too much memory. sas.exe is shown to use only about 80M. &lt;BR /&gt;
If I cancel the data step, if the memory usage is at 81% at the time, then it stops there while the confirmation window pops up. After I confirm the cancellation, the memory usage drops back.&lt;BR /&gt;
I never had this issue with SAS 9.1.3 on vista x32. I have tried everything I could think of and searched extensively but haven't found a solution, and my research is stuck because of that. If any one has any insights, it would help immensely. &lt;BR /&gt;
I've uploaded a screen capture to highlight what's going on:&lt;BR /&gt;
&lt;A href="http://screencast.com/t/pDSYT6nvf" target="_blank"&gt;http://screencast.com/t/pDSYT6nvf&lt;/A&gt;&lt;BR /&gt;
Thanks.</description>
      <pubDate>Wed, 05 Aug 2009 03:55:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/vista-x64-memory-overload/m-p/61627#M17500</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-08-05T03:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: vista x64 memory overload</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/vista-x64-memory-overload/m-p/61628#M17501</link>
      <description>sounds like a real reason to ask the experts via Customer Support, or the forms at &lt;A href="http://support.sas.com/techsup/contact/" target="_blank"&gt;http://support.sas.com/techsup/contact/&lt;/A&gt;</description>
      <pubDate>Wed, 05 Aug 2009 12:53:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/vista-x64-memory-overload/m-p/61628#M17501</guid>
      <dc:creator>Peter_C</dc:creator>
      <dc:date>2009-08-05T12:53:36Z</dc:date>
    </item>
  </channel>
</rss>

