<?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 PROC PYTHON on SAS Viya (Stable 2025.06): need to load entire ~80GB SAS table into pandas in SAS Data Science</title>
    <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-PYTHON-on-SAS-Viya-Stable-2025-06-need-to-load-entire-80GB/m-p/983134#M11116</link>
    <description>&lt;DIV&gt;&lt;SPAN&gt;Environment&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; SAS Viya: Stable 2025.06&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Using PROC PYTHON in SAS Studio (Compute)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Goal: materialize a large SAS table (~80GB) as a pandas DataFrame&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;What I tried (works on small samples, fails before completion on ~80GB):&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;1)&lt;/SPAN&gt;&lt;SPAN&gt; PROC PYTHON callback: SAS.sd2df('LIB.TABLE') &amp;nbsp;(SAS↔pandas bridge) &lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;2)&lt;/SPAN&gt;&lt;SPAN&gt; pandas.read_sas('.../file.sas7bdat') from a filesystem path&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;3)&lt;/SPAN&gt;&lt;SPAN&gt; SWAT from CAS (connects fine; pulling the full table to pandas fails)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; What’s the proven approach to fully load ~80GB into pandas within Viya?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Which admin/infra settings should be adjusted in Compute/CAS to support this (memory limits, timeouts, I/O, pod/context config)?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; For PROC PYTHON callbacks: any known limits that could explain early failures on big tables?&lt;/SPAN&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 06 Feb 2026 15:53:14 GMT</pubDate>
    <dc:creator>Zaid_Sanchez</dc:creator>
    <dc:date>2026-02-06T15:53:14Z</dc:date>
    <item>
      <title>PROC PYTHON on SAS Viya (Stable 2025.06): need to load entire ~80GB SAS table into pandas</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-PYTHON-on-SAS-Viya-Stable-2025-06-need-to-load-entire-80GB/m-p/983134#M11116</link>
      <description>&lt;DIV&gt;&lt;SPAN&gt;Environment&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; SAS Viya: Stable 2025.06&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Using PROC PYTHON in SAS Studio (Compute)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Goal: materialize a large SAS table (~80GB) as a pandas DataFrame&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;What I tried (works on small samples, fails before completion on ~80GB):&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;1)&lt;/SPAN&gt;&lt;SPAN&gt; PROC PYTHON callback: SAS.sd2df('LIB.TABLE') &amp;nbsp;(SAS↔pandas bridge) &lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;2)&lt;/SPAN&gt;&lt;SPAN&gt; pandas.read_sas('.../file.sas7bdat') from a filesystem path&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;3)&lt;/SPAN&gt;&lt;SPAN&gt; SWAT from CAS (connects fine; pulling the full table to pandas fails)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; What’s the proven approach to fully load ~80GB into pandas within Viya?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; Which admin/infra settings should be adjusted in Compute/CAS to support this (memory limits, timeouts, I/O, pod/context config)?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;-&lt;/SPAN&gt;&lt;SPAN&gt; For PROC PYTHON callbacks: any known limits that could explain early failures on big tables?&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 06 Feb 2026 15:53:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/PROC-PYTHON-on-SAS-Viya-Stable-2025-06-need-to-load-entire-80GB/m-p/983134#M11116</guid>
      <dc:creator>Zaid_Sanchez</dc:creator>
      <dc:date>2026-02-06T15:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: PROC PYTHON on SAS Viya (Stable 2025.06): need to load entire ~80GB SAS table into pandas</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/PROC-PYTHON-on-SAS-Viya-Stable-2025-06-need-to-load-entire-80GB/m-p/983137#M11117</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/480286"&gt;@Zaid_Sanchez&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While this does not directly answers your questions, but I hope it gives you another perspective to consider.&lt;/P&gt;&lt;P&gt;Check this article&amp;nbsp;&lt;A href="https://communities.sas.com/t5/SAS-Communities-Library/Parquet-Support-in-SAS-Compute-Server/ta-p/811733" target="_blank"&gt;Parquet Support in SAS Compute Server&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you convert your 80 GB *.sas7bdat file to parquet first, then you would be able to use various Python DataFrame packages beside Pandas to read that Parquet file, even if it was larger than the available RAM in the SAS Compute machine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 18:47:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/PROC-PYTHON-on-SAS-Viya-Stable-2025-06-need-to-load-entire-80GB/m-p/983137#M11117</guid>
      <dc:creator>ahmedalattar</dc:creator>
      <dc:date>2026-02-06T18:47:28Z</dc:date>
    </item>
  </channel>
</rss>

