<?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: SybaseIQ and SAS Enterprise Guide in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441984#M69264</link>
    <description>&lt;P&gt;Can you post an example of a SybaseIQ READ statement? Normally non-standard SQL can be executed via SAS's PASSTHRU EXECUTE statement.&lt;/P&gt;</description>
    <pubDate>Sat, 03 Mar 2018 00:42:29 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2018-03-03T00:42:29Z</dc:date>
    <item>
      <title>SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441980#M69263</link>
      <description>&lt;P&gt;I have a number of large SybaseIQ SQL scripts (5000+ lines each). The READ statement for each contains a number of parameters. Is there a way to execute the READ through the Proc SQL procedure using the SAS/ACCESS for SybaseIQ interface?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;many thanks in advance&lt;/P&gt;&lt;P&gt;K&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 00:27:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441980#M69263</guid>
      <dc:creator>ksamm</dc:creator>
      <dc:date>2018-03-03T00:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441984#M69264</link>
      <description>&lt;P&gt;Can you post an example of a SybaseIQ READ statement? Normally non-standard SQL can be executed via SAS's PASSTHRU EXECUTE statement.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 00:42:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441984#M69264</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-03T00:42:29Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441988#M69267</link>
      <description>Thanks for looking at this !!!&lt;BR /&gt;&lt;BR /&gt;parameters parm1 parm2&lt;BR /&gt;read ‘’ {source}&lt;BR /&gt;[parm1]&lt;BR /&gt;[parm2]&lt;BR /&gt;{output}&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 03 Mar 2018 01:14:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441988#M69267</guid>
      <dc:creator>ksamm</dc:creator>
      <dc:date>2018-03-03T01:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441994#M69269</link>
      <description>&lt;P&gt;Here is how you do an EXECUTE statement. All you need to do is put your Sybase code inside the brackets. Does this produce a result set by the way? If so then you may need to take a different approach.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://documentation.sas.com/?docsetId=acreldb&amp;amp;docsetTarget=n0pj5uu3i328pmn1fackclh2xnd9.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en" target="_self"&gt;documentation.sas.com/?docsetId=acreldb&amp;amp;docsetTarget=n0pj5uu3i328pmn1fackclh2xnd9.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 01:59:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/441994#M69269</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-03T01:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442000#M69272</link>
      <description>&lt;P&gt;Thanks SAS Kiwi,&lt;/P&gt;&lt;P&gt;Yes it produces a very large result set. Also, inserting the code between braces is not practical because as I mentioned, some of these queries are 5000+ lines long.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;K&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 02:18:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442000#M69272</guid>
      <dc:creator>ksamm</dc:creator>
      <dc:date>2018-03-03T02:18:09Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442001#M69273</link>
      <description>&lt;P&gt;You could wrap the SQL code into an SQL stored procedure, then call that. You will also need to create a temporary table or view instead of producing a result set and then query the table / view in a following "normal" SQL passthru query.&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 02:26:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442001#M69273</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-03T02:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442003#M69274</link>
      <description>&lt;P&gt;Good idea !!&amp;nbsp; This sounds feasible, I'll give it a go on Monday and let you know how it goes.&amp;nbsp; However I think there is still one potential issue which I forgot to mention earlier.&amp;nbsp; Some of the parameters to the SQL script need to bee macro variables. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 Mar 2018 02:33:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442003#M69274</guid>
      <dc:creator>ksamm</dc:creator>
      <dc:date>2018-03-03T02:33:27Z</dc:date>
    </item>
    <item>
      <title>Re: SybaseIQ and SAS Enterprise Guide</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442006#M69275</link>
      <description>&lt;P&gt;Shouldn't be a problem. The usual hassle is most databases require parameters to be wrapped in single quotes but this technique gets around that problem:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%str(%')&amp;amp;MyMacroVar%str(%')&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 03 Mar 2018 02:39:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SybaseIQ-and-SAS-Enterprise-Guide/m-p/442006#M69275</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-03T02:39:34Z</dc:date>
    </item>
  </channel>
</rss>

