<?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: Changes in native SQL on Hana in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635984#M1942701</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This remark applies only if the target DBMS for the native SQL or the ADBC interface is a SAP HANA database.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;If you switch your database on which your Netweaver stack runs and you used DBLINK before to connect to another Oracle DB, you now have to change the SQL code to confirm to SAP HANA SQL dialect.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Also, there is no DBLINK in SAP HANA - but you could use smart data access to achieve a similar integration.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Apr 2016 17:10:31 GMT</pubDate>
    <dc:creator>lbreddemann</dc:creator>
    <dc:date>2016-04-07T17:10:31Z</dc:date>
    <item>
      <title>Changes in native SQL on Hana</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635983#M1942700</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here in my company, we have a lot of native sql code to connect with a non SAP systems that uses oracle DB. This connections are made using db link on oracle.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a document that I read said:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
&lt;P&gt;Native SQL statements embedded in OpenSQL or called via the ADBC interface must be migrated to HANA Native SQL or OpenSQL and w&lt;SPAN style="font-size: 10pt;"&gt;ith Netweaver 7.40 SP5 OpenSQL got extended, to help to convert native SQL to OpenSQL&lt;/SPAN&gt;&lt;/P&gt;

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On a scenario of switch on hana, how can I adapt this codes? How can I keep this connections? What yours suggest to do in this scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you all!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 11:42:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635983#M1942700</guid>
      <dc:creator>balbino_soaresferreirafil</dc:creator>
      <dc:date>2016-04-07T11:42:03Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in native SQL on Hana</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635984#M1942701</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This remark applies only if the target DBMS for the native SQL or the ADBC interface is a SAP HANA database.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;If you switch your database on which your Netweaver stack runs and you used DBLINK before to connect to another Oracle DB, you now have to change the SQL code to confirm to SAP HANA SQL dialect.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Also, there is no DBLINK in SAP HANA - but you could use smart data access to achieve a similar integration.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Apr 2016 17:10:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635984#M1942701</guid>
      <dc:creator>lbreddemann</dc:creator>
      <dc:date>2016-04-07T17:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in native SQL on Hana</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635985#M1942702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply Lars, was very helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using the smart data access, I will need make any changes in my abap code, for exemple, can i keep the sql syntax for oracle, if the tables that I will use still in oracle? Or it will be transparent, needing only database configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I say this, only in a scenario of connection with a non sap system.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 16:25:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/changes-in-native-sql-on-hana/m-p/11635985#M1942702</guid>
      <dc:creator>balbino_soaresferreirafil</dc:creator>
      <dc:date>2016-04-08T16:25:53Z</dc:date>
    </item>
  </channel>
</rss>

