<?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: Are there ANY adverse effects to using by statement's NOTSORTED option? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Are-there-ANY-adverse-effects-to-using-by-statement-s-NOTSORTED/m-p/95877#M20160</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The option NOTSORTED cannot be used when the ordering of two or more datasets needs to be the same. You cannot use it in a datastep with MERGE and UPDATE. You can make NOTSORTED the default with global option NOBYSORTED.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More generally, I find the default option (that the observations are sorted by the BY variables) a useful safeguard against accidental reordering, as can happen for example as the result of a SQL query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 03 Feb 2013 18:01:23 GMT</pubDate>
    <dc:creator>PGStats</dc:creator>
    <dc:date>2013-02-03T18:01:23Z</dc:date>
    <item>
      <title>Are there ANY adverse effects to using by statement's NOTSORTED option?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Are-there-ANY-adverse-effects-to-using-by-statement-s-NOTSORTED/m-p/95876#M20159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can't recall if this question has ever being asked. When one includes a by statement in a procedure, and follows the by variable names with the option NOTSORTED, and the data are sorted, the option doesn't appear to have any adverse effect.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Does it have any effect(s) I'm not aware of?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2013 14:59:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Are-there-ANY-adverse-effects-to-using-by-statement-s-NOTSORTED/m-p/95876#M20159</guid>
      <dc:creator>art297</dc:creator>
      <dc:date>2013-02-03T14:59:11Z</dc:date>
    </item>
    <item>
      <title>Re: Are there ANY adverse effects to using by statement's NOTSORTED option?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Are-there-ANY-adverse-effects-to-using-by-statement-s-NOTSORTED/m-p/95877#M20160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good question!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The option NOTSORTED cannot be used when the ordering of two or more datasets needs to be the same. You cannot use it in a datastep with MERGE and UPDATE. You can make NOTSORTED the default with global option NOBYSORTED.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More generally, I find the default option (that the observations are sorted by the BY variables) a useful safeguard against accidental reordering, as can happen for example as the result of a SQL query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PG&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Feb 2013 18:01:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Are-there-ANY-adverse-effects-to-using-by-statement-s-NOTSORTED/m-p/95877#M20160</guid>
      <dc:creator>PGStats</dc:creator>
      <dc:date>2013-02-03T18:01:23Z</dc:date>
    </item>
  </channel>
</rss>

