<?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: Proc Freq - Error: Table too large to process in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86076#M24574</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the data requires too much memory to process, one approach to work around it is to use extra CPU time instead of memory.&amp;nbsp; In the extreme, you could sort your data by all 27 variables, and then use a DATA step with a BY statement to count observations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively, if by some chance your data are already in order by one of the variables, you could use that as a BY variable in PROC FREQ (or PROC SUMMARY for that matter).&amp;nbsp; For example, if your data were in order by r_HPV_recode_1, but not in order by any of the other variables, you could use:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc freq data=hpv_single_reasons;&lt;/P&gt;&lt;P&gt;&amp;nbsp; by r_HPV_recode_1;&lt;/P&gt;&lt;P&gt;&amp;nbsp; tables (same list, but remove r_HPV_recode_1) / out=hpv_single_reasons;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The counts will be the same as if your original program had worked, although the percentages will be different.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's no guarantee it will work, but it certainly has a good chance.&amp;nbsp; You might have to switch 2 or 3 variables to the BY statement instead of just 1, in which case the SORT + DATA step might be preferable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 Jun 2012 15:17:12 GMT</pubDate>
    <dc:creator>Astounding</dc:creator>
    <dc:date>2012-06-18T15:17:12Z</dc:date>
    <item>
      <title>Proc Freq - Error: Table too large to process</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86074#M24572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to create an output dataset of the following variable comparisons using proc freq. I am able to do this with one subset of my population which is small, but when I run the same coding on the larger dataset, the error that the table is too large to process appears in the log. Is there a way to fix this in a setting or do I need to try and create the variable comparisons in a different program? Thank you for any help you can give. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc freq data=hpv_single_reasons;&lt;/P&gt;&lt;P&gt;tables r_HPV_recode_1*r_HPV_recode_2*r_HPV_recode_3*r_HPV_recode_4*r_HPV_recode_5*r_HPV_recode_6*r_HPV_recode_7*r_HPV_recode_8*&lt;/P&gt;&lt;P&gt;r_HPV_recode_9*r_HPV_recode_10*r_HPV_recode_11*r_HPV_recode_12*r_HPV_recode_13*r_HPV_recode_14*r_HPV_recode_15*r_HPV_recode_16*&lt;/P&gt;&lt;P&gt;r_HPV_recode_17*r_HPV_recode_18*r_HPV_recode_19*r_HPV_recode_20*r_HPV_recode_21*r_HPV_recode_22*r_HPV_recode_23*r_HPV_recode_24*&lt;/P&gt;&lt;P&gt;r_HPV_recode_25*r_HPV_recode_26*r_HPV_recode_27/noprint out = hpv_single_reasons;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 14:11:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86074#M24572</guid>
      <dc:creator>HyunJee</dc:creator>
      <dc:date>2012-06-18T14:11:45Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Freq - Error: Table too large to process</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86075#M24573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think Proc Freq might be trying to utilize memory to fit all the combinations of class variables in it.&lt;/P&gt;&lt;P&gt;Have you tried Proc Summary instead? It will provide you the counts not the percentages which can be computed easily once you get the counts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc summary data=hpv_single_reasons nway missing;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; class&amp;nbsp; r_HPV_recode_1 r_HPV_recode_2 r_HPV_recode_3 r_HPV_recode_4 r_HPV_recode_5 r_HPV_recode_6 &lt;/P&gt;&lt;P&gt;r_HPV_recode_7 r_HPV_recode_8 r_HPV_recode_9 r_HPV_recode_10 r_HPV_recode_11 r_HPV_recode_12 r_HPV_recode_13 &lt;/P&gt;&lt;P&gt;r_HPV_recode_14 r_HPV_recode_15 r_HPV_recode_16 r_HPV_recode_17 r_HPV_recode_18 r_HPV_recode_19 &lt;/P&gt;&lt;P&gt;r_HPV_recode_20 r_HPV_recode_21 r_HPV_recode_22 r_HPV_recode_23 r_HPV_recode_24&lt;/P&gt;&lt;P&gt;r_HPV_recode_25 r_HPV_recode_26 r_HPV_recode_27;&lt;/P&gt;&lt;P&gt;output out=hpv_single_reasons(rename=_freq_=Count drop=_type_);&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 14:25:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86075#M24573</guid>
      <dc:creator>Alpay</dc:creator>
      <dc:date>2012-06-18T14:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: Proc Freq - Error: Table too large to process</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86076#M24574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the data requires too much memory to process, one approach to work around it is to use extra CPU time instead of memory.&amp;nbsp; In the extreme, you could sort your data by all 27 variables, and then use a DATA step with a BY statement to count observations. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively, if by some chance your data are already in order by one of the variables, you could use that as a BY variable in PROC FREQ (or PROC SUMMARY for that matter).&amp;nbsp; For example, if your data were in order by r_HPV_recode_1, but not in order by any of the other variables, you could use:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc freq data=hpv_single_reasons;&lt;/P&gt;&lt;P&gt;&amp;nbsp; by r_HPV_recode_1;&lt;/P&gt;&lt;P&gt;&amp;nbsp; tables (same list, but remove r_HPV_recode_1) / out=hpv_single_reasons;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The counts will be the same as if your original program had worked, although the percentages will be different.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's no guarantee it will work, but it certainly has a good chance.&amp;nbsp; You might have to switch 2 or 3 variables to the BY statement instead of just 1, in which case the SORT + DATA step might be preferable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 15:17:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/Proc-Freq-Error-Table-too-large-to-process/m-p/86076#M24574</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2012-06-18T15:17:12Z</dc:date>
    </item>
  </channel>
</rss>

