<?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 Data Migration Netezza to Exadata in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Data-Migration-Netezza-to-Exadata/m-p/2207784#M7282</link>
    <description>&lt;P&gt;Hi Gurus,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As part of data migration, if I have to replace netezza components to oracle components. Eg: tNetezzaInput to tOracaleinput.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please need some information on Netezza Components NOT compatible with Oracle Components.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eg: tNetezzaNZload we don't have option in Oracle components.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, please let us know if you have encountered any other issues during this process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank You!!&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 06:47:47 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2024-11-16T06:47:47Z</dc:date>
    <item>
      <title>Data Migration Netezza to Exadata</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Data-Migration-Netezza-to-Exadata/m-p/2207784#M7282</link>
      <description>&lt;P&gt;Hi Gurus,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As part of data migration, if I have to replace netezza components to oracle components. Eg: tNetezzaInput to tOracaleinput.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please need some information on Netezza Components NOT compatible with Oracle Components.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Eg: tNetezzaNZload we don't have option in Oracle components.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, please let us know if you have encountered any other issues during this process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank You!!&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 06:47:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Data-Migration-Netezza-to-Exadata/m-p/2207784#M7282</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-16T06:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Data Migration Netezza to Exadata</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Data-Migration-Netezza-to-Exadata/m-p/2207785#M7283</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.qlik.com/s/profile/0053p000007LPByAAO"&gt;@Srigha&lt;/A&gt;&amp;nbsp;,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;Oracle and Netezza works in totally different way like the way of working on primary keys. So if you are planing for a migration, even though you are replacing a tNetezzaInput to tOracleInput, you need to see the data fetch and performance since the optimizer works in different ways in both DBs.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;In simple words, a Netezza specific operations in your code will not work in Oracle after migration. So unless your SQL is database neutral, you will have to do the testing of your flows for migration. There are no short cuts in it as it is DB specific constraints where Talend do not have any control.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;Warm Regards,&lt;BR /&gt;Nikhil Thampi&lt;/P&gt; 
&lt;P&gt;Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jan 2019 06:49:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Data-Migration-Netezza-to-Exadata/m-p/2207785#M7283</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-01-23T06:49:05Z</dc:date>
    </item>
  </channel>
</rss>

