<?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: A problem with integrity constraint in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/A-problem-with-integrity-constraint/m-p/65089#M18550</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Try to check the columns of your target table. probably some of your columns should not contain a null value and then you try to insert records with a null value on that particular column. Hope this helps.&lt;BR /&gt;
&lt;BR /&gt;
regards,&lt;BR /&gt;
milton</description>
    <pubDate>Tue, 18 Aug 2009 09:54:29 GMT</pubDate>
    <dc:creator>milts</dc:creator>
    <dc:date>2009-08-18T09:54:29Z</dc:date>
    <item>
      <title>A problem with integrity constraint</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/A-problem-with-integrity-constraint/m-p/65088#M18549</link>
      <description>Hi guys,&lt;BR /&gt;
&lt;BR /&gt;
I have encounter a problem in SAS data integration studio 3.4.&lt;BR /&gt;
&lt;BR /&gt;
The problem is like this. After a transformation, all the data will output into an temp target table. Then I load this data using the table loader into the target table&lt;BR /&gt;
&lt;BR /&gt;
Before I loaded into the target table, the temp target table has 80000 records.&lt;BR /&gt;
&lt;BR /&gt;
After I loaded into the target table, the target table has 70000 records.&lt;BR /&gt;
&lt;BR /&gt;
It is due to:&lt;BR /&gt;
 &lt;BR /&gt;
WARNING: Add/Update failed for data set STG_SEAB.PERSONAL because data value(s) do not comply with integrity constraint _NM0001_. &lt;BR /&gt;
         (Occurred 498 times.)&lt;BR /&gt;
&lt;BR /&gt;
WARNING: Add/Update failed for data set STG_SEAB.PERSONAL because data value(s) do not comply with integrity constraint _NM0002_. &lt;BR /&gt;
         (Occurred 9312 times.)&lt;BR /&gt;
&lt;BR /&gt;
So how to solve this problem?&lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;BR /&gt;
&lt;BR /&gt;
Yours Sincerely,&lt;BR /&gt;
helphelp</description>
      <pubDate>Tue, 18 Aug 2009 08:39:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/A-problem-with-integrity-constraint/m-p/65088#M18549</guid>
      <dc:creator>deleted_user</dc:creator>
      <dc:date>2009-08-18T08:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: A problem with integrity constraint</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/A-problem-with-integrity-constraint/m-p/65089#M18550</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Try to check the columns of your target table. probably some of your columns should not contain a null value and then you try to insert records with a null value on that particular column. Hope this helps.&lt;BR /&gt;
&lt;BR /&gt;
regards,&lt;BR /&gt;
milton</description>
      <pubDate>Tue, 18 Aug 2009 09:54:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/A-problem-with-integrity-constraint/m-p/65089#M18550</guid>
      <dc:creator>milts</dc:creator>
      <dc:date>2009-08-18T09:54:29Z</dc:date>
    </item>
  </channel>
</rss>

