<?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: run selected code in Proc SQL in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407887#M26177</link>
    <description>&lt;P&gt;Another option is SAS Studio. Apparently it has an "interactive mode", where an interactive procedure won't be terminated when submitted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can't test this, as I'm using Studio with SAS On Demand, which doesn't allow interactive mode.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Fri, 27 Oct 2017 01:51:24 GMT</pubDate>
    <dc:creator>TomKari</dc:creator>
    <dc:date>2017-10-27T01:51:24Z</dc:date>
    <item>
      <title>run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407845#M26169</link>
      <description>&lt;P&gt;In PC SAS, under one PROC SQL ... QUIT, we can select a particular set of codes and execute it, then do the same thing for another selected code, and etc.. But it looks this feature does not work in&amp;nbsp;SAS EG, we have to run the entire Proc SQL, which makes the code testing process a little bit difficult, especially when it involves Teradata volatile table for instance.&lt;/P&gt;&lt;P&gt;Is there an option in SAS EG to turn this PC SAS feature on?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2017 21:53:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407845#M26169</guid>
      <dc:creator>yizhusas</dc:creator>
      <dc:date>2017-10-26T21:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407849#M26170</link>
      <description>&lt;P&gt;No. Since EG sends "magic code" that is designed to clean up after any mistake, it also ends proc sql with quit;&lt;/P&gt;
&lt;P&gt;To selectively run individual SQL steps, you have to wrap them into individual proc sql calls.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2017 22:05:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407849#M26170</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2017-10-26T22:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407852#M26171</link>
      <description>&lt;P&gt;that's bad. The problem is whenever we hit the quit, the volatile table will be gone, so I have no way to bring it into next proc sql. Hopefully SAS&amp;nbsp;will add that&amp;nbsp;feature&amp;nbsp;into&amp;nbsp;its future version of SAS EG.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2017 22:16:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407852#M26171</guid>
      <dc:creator>yizhusas</dc:creator>
      <dc:date>2017-10-26T22:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407865#M26172</link>
      <description>&lt;P&gt;That actually sounds like something you may also be able to fix on the Teradata side, can you get your volatile tables to basically not be volatile and exist past a single session. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2017 23:55:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407865#M26172</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2017-10-26T23:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407871#M26173</link>
      <description>&lt;P&gt;figured it out. Actually I have to set my v-table as global by using the option&amp;nbsp;"connection=global" in proc sql, then the v-table can be used in separated proc sql.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 00:11:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407871#M26173</guid>
      <dc:creator>yizhusas</dc:creator>
      <dc:date>2017-10-27T00:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407873#M26174</link>
      <description>&lt;P&gt;Are you using implicit pass through or explicit through for accessing volatile table? if it is explicit pass through run the queries in sql assistant and then all u need to do is wrap work execute and by teradata at the end.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 00:17:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407873#M26174</guid>
      <dc:creator>kiranv_</dc:creator>
      <dc:date>2017-10-27T00:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407874#M26175</link>
      <description>&lt;P&gt;one more thing you can use your volatile table in SAS in datastep or implicit pass through by using dbmstemp =yes. see the link below for more details&lt;/P&gt;
&lt;P&gt;&lt;A href="http://documentation.sas.com/?docsetId=acreldb&amp;amp;docsetTarget=p0he4t6yjfmkhpn16qrf0cdhllu6.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en" target="_blank"&gt;http://documentation.sas.com/?docsetId=acreldb&amp;amp;docsetTarget=p0he4t6yjfmkhpn16qrf0cdhllu6.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 00:20:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407874#M26175</guid>
      <dc:creator>kiranv_</dc:creator>
      <dc:date>2017-10-27T00:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407875#M26176</link>
      <description>&lt;P&gt;absolutely it won't work without "dbmstemp=yes", I am using the&amp;nbsp;&lt;SPAN&gt;explicit through.&amp;nbsp;&amp;nbsp;Have to define the libname first with the opinion "dbmstemp=yes" along with other teradata login&amp;nbsp;statement.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 00:29:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407875#M26176</guid>
      <dc:creator>yizhusas</dc:creator>
      <dc:date>2017-10-27T00:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: run selected code in Proc SQL</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407887#M26177</link>
      <description>&lt;P&gt;Another option is SAS Studio. Apparently it has an "interactive mode", where an interactive procedure won't be terminated when submitted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can't test this, as I'm using Studio with SAS On Demand, which doesn't allow interactive mode.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Fri, 27 Oct 2017 01:51:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/run-selected-code-in-Proc-SQL/m-p/407887#M26177</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2017-10-27T01:51:24Z</dc:date>
    </item>
  </channel>
</rss>

