<?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 &amp;quot;Duplicate values not allowed&amp;quot; on my pk_index in DI Studio in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/quot-Duplicate-values-not-allowed-quot-on-my-pk-index-in-DI/m-p/81308#M727</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've created a job that's using a composite PK which includes eight variables. When I run the job, the final Table Loader generates an error message telling me&amp;nbsp; "Duplicate values not allowed on index pk_index for file MYTABLENAME." The Constraint- and Index Conditions of the Table Loader are both set to "After Load: On (table creation)". What is a good way to resolve this situation? I've never handled something like this before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Oct 2012 08:19:49 GMT</pubDate>
    <dc:creator>EinarRoed</dc:creator>
    <dc:date>2012-10-01T08:19:49Z</dc:date>
    <item>
      <title>"Duplicate values not allowed" on my pk_index in DI Studio</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/quot-Duplicate-values-not-allowed-quot-on-my-pk-index-in-DI/m-p/81308#M727</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've created a job that's using a composite PK which includes eight variables. When I run the job, the final Table Loader generates an error message telling me&amp;nbsp; "Duplicate values not allowed on index pk_index for file MYTABLENAME." The Constraint- and Index Conditions of the Table Loader are both set to "After Load: On (table creation)". What is a good way to resolve this situation? I've never handled something like this before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2012 08:19:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/quot-Duplicate-values-not-allowed-quot-on-my-pk-index-in-DI/m-p/81308#M727</guid>
      <dc:creator>EinarRoed</dc:creator>
      <dc:date>2012-10-01T08:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: "Duplicate values not allowed" on my pk_index in DI Studio</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/quot-Duplicate-values-not-allowed-quot-on-my-pk-index-in-DI/m-p/81309#M728</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Obviously, you have duplicate values in your source data.&lt;/P&gt;&lt;P&gt;How to handle this is a matter of process.&lt;/P&gt;&lt;P&gt;Perhaps you have the source data i some kind of staging table, which will make it easy to examine and determine the duplicates.&lt;/P&gt;&lt;P&gt;If duplicates are common, you could add some logic in your flows to find the duplicates prior to the loading step, hand have them stored in a separate table. The Data validation transformation could be used for this.&lt;/P&gt;&lt;P&gt;About the constraints, what is the requirement to handle data quality? Having constraints on a target like this is like a guarantee that the data is consistent. You pay with a little overhead during load. The trade off is when to restore or in other ways clean up the target table after a load of duplicate values.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Oct 2012 09:07:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/quot-Duplicate-values-not-allowed-quot-on-my-pk-index-in-DI/m-p/81309#M728</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2012-10-01T09:07:00Z</dc:date>
    </item>
  </channel>
</rss>

