<?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 DS2: BASE driver, creation of a INTEGER column has been requested in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/proc-DS2-BASE-driver-creation-of-a-INTEGER-column-has-been/m-p/259029#M50038</link>
    <description>&lt;P&gt;Base SAS only knows two data types, character and numeric. All numeric variables are always stored as 8-byte (or less, if you specify it with a LENGTH statement) &lt;U&gt;real&lt;/U&gt; (mantissa and exponent) numbers. All SAS tables are stored with these limits.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So the note just informs you that your numbers will be stored that way; since there is no other option, there is also no performance penalty or other negative effect. Just keep in mind that you may run into &lt;U&gt;precision&lt;/U&gt; problems a little earlier than the overflow error you'd expect with 8-byte integers.&lt;/P&gt;
&lt;P&gt;To avoid the NOTE, just stay with double.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then why is "integer" there at all? If you run PROC DS2 against a table that is not a native SAS table, but in a database, and the database engine supports integer, then it will have an effect.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Mar 2016 09:51:41 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2016-03-25T09:51:41Z</dc:date>
    <item>
      <title>proc DS2: BASE driver, creation of a INTEGER column has been requested</title>
      <link>https://communities.sas.com/t5/SAS-Programming/proc-DS2-BASE-driver-creation-of-a-INTEGER-column-has-been/m-p/259015#M50031</link>
      <description>&lt;P&gt;First things first. The SAS version of our company:&amp;nbsp;9.04.01M3P062415&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whenever using non double variables in proc ds2 variables like integer or dates, i.e.:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc ds2 scond = error;
	data test (overwrite=yes);
		declare integer a b d;

		method run();
                        a = 3;
                        b = 4;
			d = a + b;
			output;
		end;
	enddata;
run;
quit;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I get the following Note in my log:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;NOTE: BASE driver, creation of a INTEGER column has been requested, but is not supported by the BASE driver. A DOUBLE PRECISION 
      column has been created instead.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When solely using &amp;nbsp;double variables the&amp;nbsp;proc ds2 runs smoothly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there anything I can do to prevent this note? Does it have and impact on the performance or should I just ignore it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd be thankful for any hint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 05:36:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/proc-DS2-BASE-driver-creation-of-a-INTEGER-column-has-been/m-p/259015#M50031</guid>
      <dc:creator>Alkibiades</dc:creator>
      <dc:date>2016-03-25T05:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: proc DS2: BASE driver, creation of a INTEGER column has been requested</title>
      <link>https://communities.sas.com/t5/SAS-Programming/proc-DS2-BASE-driver-creation-of-a-INTEGER-column-has-been/m-p/259029#M50038</link>
      <description>&lt;P&gt;Base SAS only knows two data types, character and numeric. All numeric variables are always stored as 8-byte (or less, if you specify it with a LENGTH statement) &lt;U&gt;real&lt;/U&gt; (mantissa and exponent) numbers. All SAS tables are stored with these limits.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So the note just informs you that your numbers will be stored that way; since there is no other option, there is also no performance penalty or other negative effect. Just keep in mind that you may run into &lt;U&gt;precision&lt;/U&gt; problems a little earlier than the overflow error you'd expect with 8-byte integers.&lt;/P&gt;
&lt;P&gt;To avoid the NOTE, just stay with double.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then why is "integer" there at all? If you run PROC DS2 against a table that is not a native SAS table, but in a database, and the database engine supports integer, then it will have an effect.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2016 09:51:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/proc-DS2-BASE-driver-creation-of-a-INTEGER-column-has-been/m-p/259029#M50038</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2016-03-25T09:51:41Z</dc:date>
    </item>
  </channel>
</rss>

