<?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: SAS LASR Memory Alternatives in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292443#M8289</link>
    <description>&lt;P&gt;Save data on disk removes the possibility&amp;nbsp;to (immediately) analyze it in VA/VS. So it depends hon your whole analytical environment/process if that's feasible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There a few techniques (not limited to) that can save memory in LASR, what to do depends on your data, requirements and query patterns:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Compress&lt;/LI&gt;
&lt;LI&gt;Star schema&lt;/LI&gt;
&lt;LI&gt;Truncate char cols&lt;/LI&gt;
&lt;LI&gt;Use formats&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Thu, 18 Aug 2016 13:14:04 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2016-08-18T13:14:04Z</dc:date>
    <item>
      <title>SAS LASR Memory Alternatives</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292424#M8288</link>
      <description>&lt;P&gt;I need help regarding SAS memory management, currently I have 96 GB LASR memory but my production data base size is huge so currently we put only 90 days data (only important table) in SAS LASR, now LASR memory is almost full and due to this SAS server is goes down so many time, due to this all data is truncated from memory, so can you suggest me how manage SAS memory system or save data in disk other than LASR or opimization of data in LASR, any best way optimize data size of table&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;proc sql ;&lt;BR /&gt;connect to odbc (dsn=inventory user=ashu password=''); &amp;nbsp;&lt;BR /&gt;create table libname.test_table as select&lt;BR /&gt;c0&amp;nbsp; format=11.,&lt;BR /&gt;c1&amp;nbsp; format=$30. length=30,&lt;BR /&gt;c2&amp;nbsp; format=11.,&lt;BR /&gt;c3&amp;nbsp; format=11.2&lt;BR /&gt;from connection to odbc&lt;BR /&gt;(SELECT c0,c1,c2,c3&lt;BR /&gt;FROM db_name.test_table&lt;BR /&gt;limit 10;);&lt;BR /&gt;disconnect from odbc;&lt;BR /&gt;quit ;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2016 12:29:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292424#M8288</guid>
      <dc:creator>singhashupratap</dc:creator>
      <dc:date>2016-08-18T12:29:29Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LASR Memory Alternatives</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292443#M8289</link>
      <description>&lt;P&gt;Save data on disk removes the possibility&amp;nbsp;to (immediately) analyze it in VA/VS. So it depends hon your whole analytical environment/process if that's feasible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There a few techniques (not limited to) that can save memory in LASR, what to do depends on your data, requirements and query patterns:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Compress&lt;/LI&gt;
&lt;LI&gt;Star schema&lt;/LI&gt;
&lt;LI&gt;Truncate char cols&lt;/LI&gt;
&lt;LI&gt;Use formats&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 18 Aug 2016 13:14:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292443#M8289</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2016-08-18T13:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LASR Memory Alternatives</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292943#M8296</link>
      <description>&lt;P&gt;I don't have practical experience with it but it appears the 2.4 version got a &lt;EM&gt;squeeze&lt;/EM&gt; option which allows for compressed in-memory tables.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/inmsref/67597/HTML/default/viewer.htm#inmsrefwhatsnew24.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/inmsref/67597/HTML/default/viewer.htm#inmsrefwhatsnew24.htm&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 20 Aug 2016 23:46:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292943#M8296</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2016-08-20T23:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: SAS LASR Memory Alternatives</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292952#M8297</link>
      <description>&lt;P&gt;Compression is available in the more recent versions of SAS VA, but the down side is it can have a very significant impact on performance and needs to be used with extreme caution. For large tables like the one being discussed it could be a total CPU killer. Have a look at the other options suggested first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also if you don't need row-level detail in VA consider pre-summarising your data first to reduce the size.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Aug 2016 05:37:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-LASR-Memory-Alternatives/m-p/292952#M8297</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2016-08-21T05:37:15Z</dc:date>
    </item>
  </channel>
</rss>

