<?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: Importing Extremely Large Text File in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152223#M11935</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you say "\001" is the delimiter, do you mean 0x01, the SOH (start of heading) character?&amp;nbsp; I'm not sure the Import Data task can detect/support that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When using the Import Data task in EG, be sure to click the &lt;STRONG&gt;Performance&lt;/STRONG&gt; button on the first page, then check "Bypass the data cleansing process".&amp;nbsp; This will save quite a bit of overhead that you probably don't need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="5795" alt="perf.png" class="jive-image" src="https://communities.sas.com/legacyfs/online/5795_perf.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can mock up a small subset of the data file with a delimiter that EG does support, then you could use the EG task to "design" the import step, then modify a copy of the generated code to use the proper delimiter and point to the actual source file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV style="font-family: Consolas; font-size: 11pt;"&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;INFILE&lt;/SPAN&gt; &lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;'C:\data\realbigfile.txt'&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;LRECL&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;STRONG style="color: #008080; background-color: #ffffff;"&gt;32767&lt;/STRONG&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;ENCODING&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;"WLATIN1"&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;DLM&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;'01'x&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;MISSOVER&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;DSD&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt; ;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your EG is local and your SAS server is remote, and you need the text file to get "moved" to the server for import, consider using &lt;A href="http://blogs.sas.com/content/sasdummy/2012/12/06/copy-files-in-sas-eg/"&gt;the Copy Files task&lt;/A&gt; to perform that part.&amp;nbsp; However, you'll need a good chunk of temp space to hold a 12GB file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Mar 2014 16:50:06 GMT</pubDate>
    <dc:creator>ChrisHemedinger</dc:creator>
    <dc:date>2014-03-21T16:50:06Z</dc:date>
    <item>
      <title>Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152222#M11934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all --&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been having a tough time trying to import a huge text file, it's around 12GB and roughly 35 million rows -- my goal is to simply create an indexed SAS dataset for a data library.&amp;nbsp; The file is a CSV file, "\001" as a delimiter.&amp;nbsp; I've tried multiple methods to import (wizard, infile, etc..) but I can't seem to get anything to run.&amp;nbsp; I'm looking for some tips/suggestions on how to efficiently import this file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there other tools that are better suited for the job?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 16:33:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152222#M11934</guid>
      <dc:creator>mdavidson</dc:creator>
      <dc:date>2014-03-21T16:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152223#M11935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you say "\001" is the delimiter, do you mean 0x01, the SOH (start of heading) character?&amp;nbsp; I'm not sure the Import Data task can detect/support that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When using the Import Data task in EG, be sure to click the &lt;STRONG&gt;Performance&lt;/STRONG&gt; button on the first page, then check "Bypass the data cleansing process".&amp;nbsp; This will save quite a bit of overhead that you probably don't need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="5795" alt="perf.png" class="jive-image" src="https://communities.sas.com/legacyfs/online/5795_perf.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can mock up a small subset of the data file with a delimiter that EG does support, then you could use the EG task to "design" the import step, then modify a copy of the generated code to use the proper delimiter and point to the actual source file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV style="font-family: Consolas; font-size: 11pt;"&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;INFILE&lt;/SPAN&gt; &lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;'C:\data\realbigfile.txt'&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;LRECL&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;STRONG style="color: #008080; background-color: #ffffff;"&gt;32767&lt;/STRONG&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;ENCODING&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;"WLATIN1"&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;DLM&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;=&lt;/SPAN&gt;&lt;SPAN style="color: #800080; background-color: #ffffff;"&gt;'01'x&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;MISSOVER&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;SPAN style="color: #0000ff; background-color: #ffffff;"&gt;DSD&lt;/SPAN&gt;&lt;SPAN style="color: #000000; background-color: #ffffff;"&gt; ;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your EG is local and your SAS server is remote, and you need the text file to get "moved" to the server for import, consider using &lt;A href="http://blogs.sas.com/content/sasdummy/2012/12/06/copy-files-in-sas-eg/"&gt;the Copy Files task&lt;/A&gt; to perform that part.&amp;nbsp; However, you'll need a good chunk of temp space to hold a 12GB file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 16:50:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152223#M11935</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2014-03-21T16:50:06Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152224#M11936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the response Chris.&amp;nbsp; Yes you're correct that&lt;SPAN style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: #ffffff;"&gt; my delimited is 0x01, the SOH (start of heading) character, sorry for the confusion.&amp;nbsp; I attempted to import a small subset of my data using the import wizard, and you're correct in that the data task does not support that type of delimiter. On the infile statement is '01'x the delimiter I want to use in this case?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 17:10:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152224#M11936</guid>
      <dc:creator>mdavidson</dc:creator>
      <dc:date>2014-03-21T17:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152225#M11937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that should do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fun fact: when EG creates a "clean, delimited version" of a raw text file for input, it uses the DEL character ('7F'x) to minimize the chance of conflicts with actual data content.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &lt;STRONG&gt;Performance&lt;/STRONG&gt; setting I described lets you skip that step -- usually a safe option when the incoming data is a clean, well-formed source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 17:16:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152225#M11937</guid>
      <dc:creator>ChrisHemedinger</dc:creator>
      <dc:date>2014-03-21T17:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152226#M11938</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Chris, your solution worked great. Only took about 5 minutes to import.&amp;nbsp; Much appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Mar 2014 19:20:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/152226#M11938</guid>
      <dc:creator>mdavidson</dc:creator>
      <dc:date>2014-03-21T19:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/355792#M23422</link>
      <description>&lt;P&gt;I have a similar situation. I am able to get passed the import wizard and create a file in SAS EG. But, SAS EG opens the imported data set by default and spends hours trying to load the file. I want to merely export the data set to a saved SAS data set. So, I don't need to display it open. I've tinkered with the SAS EG options related to Data, but nothing is helping.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 21:21:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/355792#M23422</guid>
      <dc:creator>CurtisSmithDCAA</dc:creator>
      <dc:date>2017-05-03T21:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: Importing Extremely Large Text File</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/356579#M23469</link>
      <description>&lt;P&gt;In EG's Tools-&amp;gt;Options-&amp;gt;Results-&amp;gt;Results General, unchecking &lt;STRONG&gt;Automatically open data or results when generated&lt;/STRONG&gt; should prevent the imported data set from being opened automatically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Casey&lt;/P&gt;</description>
      <pubDate>Sat, 06 May 2017 02:17:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/Importing-Extremely-Large-Text-File/m-p/356579#M23469</guid>
      <dc:creator>CaseySmith</dc:creator>
      <dc:date>2017-05-06T02:17:11Z</dc:date>
    </item>
  </channel>
</rss>

