<?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 SAS DI SQL transformation oracle connection in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/817731#M20376</link>
    <description>&lt;P&gt;Hi all, I'm trying to execute explicit SQL in Oracle with two tables with different schemas. SAS DI is using in the connection string to oracle the authdomain of the first connected source table. Is there a way to bypass this option and use the authdomain of the target table instead of the (first) connected source table?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jun 2022 09:53:39 GMT</pubDate>
    <dc:creator>JeroenPotgieter</dc:creator>
    <dc:date>2022-06-13T09:53:39Z</dc:date>
    <item>
      <title>SAS DI SQL transformation oracle connection</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/817731#M20376</link>
      <description>&lt;P&gt;Hi all, I'm trying to execute explicit SQL in Oracle with two tables with different schemas. SAS DI is using in the connection string to oracle the authdomain of the first connected source table. Is there a way to bypass this option and use the authdomain of the target table instead of the (first) connected source table?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2022 09:53:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/817731#M20376</guid>
      <dc:creator>JeroenPotgieter</dc:creator>
      <dc:date>2022-06-13T09:53:39Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DI SQL transformation oracle connection</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/817743#M20377</link>
      <description>&lt;P&gt;If you can show how you have defined the two tables in the transformation, and the generated code (with comments if needed), it would help me to understand what you are trying to do.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jun 2022 10:22:24 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/817743#M20377</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2022-06-13T10:22:24Z</dc:date>
    </item>
    <item>
      <title>Re: SAS DI SQL transformation oracle connection</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/834626#M20582</link>
      <description>&lt;P&gt;Hi Jeroen,&lt;/P&gt;
&lt;P&gt;Your post was a few months ago, and I only just came across it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SAS did add some support for this, see&amp;nbsp;&lt;A href="https://support.sas.com/kb/68/840.html" target="_blank"&gt;68840 - Database connection information for a source table is used when creating a new database table with the Create Table transformation (sas.com)&lt;/A&gt;&amp;nbsp;for a Hot Fix that might help you.&amp;nbsp; However, if that does not meet your use case, please contact your local SAS Technical Support office, maybe with a package file that shows the issue. SAS can then review and determine if we can also address your specific use case.&lt;/P&gt;
&lt;P&gt;Thanks, Mark&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2022 08:42:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SAS-DI-SQL-transformation-oracle-connection/m-p/834626#M20582</guid>
      <dc:creator>MarkDawson</dc:creator>
      <dc:date>2022-09-22T08:42:37Z</dc:date>
    </item>
  </channel>
</rss>

