<?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: Index naming in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799794#M864</link>
    <description>&lt;P&gt;Thanks John,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like I'm going to have to live with it for now. Not an issue, I just wondered if I had missed something.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ian&lt;/P&gt;</description>
    <pubDate>Thu, 15 Apr 2021 15:24:45 GMT</pubDate>
    <dc:creator>IanM</dc:creator>
    <dc:date>2021-04-15T15:24:45Z</dc:date>
    <item>
      <title>Index naming</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799751#M862</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm replicating (ver 7.0.0.213) from Oracle to Oracle and using the Drop and Create Table option.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Replicate did not automatically identify a unique index to use (I think because the source indexes are function based), so I have configured a key manually on the Transform tab.&lt;/P&gt;&lt;P&gt;Is there any control over the name it creates for the destination index?&lt;/P&gt;&lt;P&gt;Ideally I would be able to keep the naming convention of the source as it does for the automatically detected indexes.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ian&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 13:29:27 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799751#M862</guid>
      <dc:creator>IanM</dc:creator>
      <dc:date>2021-04-15T13:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Index naming</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799779#M863</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/137694"&gt;@IanM&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;Not sure what's your Oracle source table creation DDL, let's start from the general Index Naming rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. If the table has PK, then replicate defines PK in target table. No Unique Index (UI) will be created in target table.&lt;/P&gt;&lt;P&gt;2. If the table has not PK, and there is only one Unique Index in source table (as you already know,&amp;nbsp;Function-based indexes are not supported)&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Replicate will create the same UI (columns list, same below) in target table. The UI name would be like &amp;lt;target Table Name&amp;gt; + "&lt;STRONG&gt;_PK&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;3. If the table has not PK, and If there are multiple UIs in source table&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Replicate defines only one index on the target table, by default it's the first UI (according to alphabetical order) of the source table. The UI name would be like&amp;nbsp;&amp;lt;target Table Name&amp;gt; + "&lt;STRONG&gt;_PK&lt;/STRONG&gt;"&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; If you choose a non-default UI/PK, then see (4) below.&lt;/P&gt;&lt;P&gt;4. If the table has not PK, and you choose KEY in Console GUI manaually (for example, the source table has not PK/UI, or you choose a non-default UI)&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Replicate defines the index on target table, the UI name would be like&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;    &amp;lt;taget Table Name&amp;gt;+"_"+&amp;lt;unixepoch format of current time&amp;gt;+"_PK"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; By adding Unix Epoch time to make sure the UI name uniqueness.&amp;nbsp; However Replicate will truncate the UI name length to 30. For example the Index name is "KITNOUI_T_1618495151441352_PK" if you run the task around 2021.04.15T21:56:00 where the table table name is defined as "KITNOUI_T".&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately, there is no explicit easy way to control the UI name. You may raise feature request if you want. To submit Feature Requests&amp;nbsp; please use our Qlik Community "Product Insight and Ideas" forum.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 14:54:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799779#M863</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2021-04-15T14:54:48Z</dc:date>
    </item>
    <item>
      <title>Re: Index naming</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799794#M864</link>
      <description>&lt;P&gt;Thanks John,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like I'm going to have to live with it for now. Not an issue, I just wondered if I had missed something.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ian&lt;/P&gt;</description>
      <pubDate>Thu, 15 Apr 2021 15:24:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Index-naming/m-p/1799794#M864</guid>
      <dc:creator>IanM</dc:creator>
      <dc:date>2021-04-15T15:24:45Z</dc:date>
    </item>
  </channel>
</rss>

