<?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 CROSS DATABASE KEY ISSUE in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876869#M346399</link>
    <description>&lt;P&gt;I am loading sas data converted to csv into DB2. one problem is when&amp;nbsp; I setup tables in DB2, I added keys and the keys are usually the merge by columns. and these keys are not nullable. So if in sas data, key is null then when I load into DB2, the entries with null key would be rejected automatically. And my uat and prod data might not match. how can I overcome this? is it a good way if I transferred null to empty string so it wouldnt be rejected by db2?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 May 2023 09:13:03 GMT</pubDate>
    <dc:creator>HeatherNewton</dc:creator>
    <dc:date>2023-05-22T09:13:03Z</dc:date>
    <item>
      <title>CROSS DATABASE KEY ISSUE</title>
      <link>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876869#M346399</link>
      <description>&lt;P&gt;I am loading sas data converted to csv into DB2. one problem is when&amp;nbsp; I setup tables in DB2, I added keys and the keys are usually the merge by columns. and these keys are not nullable. So if in sas data, key is null then when I load into DB2, the entries with null key would be rejected automatically. And my uat and prod data might not match. how can I overcome this? is it a good way if I transferred null to empty string so it wouldnt be rejected by db2?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 09:13:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876869#M346399</guid>
      <dc:creator>HeatherNewton</dc:creator>
      <dc:date>2023-05-22T09:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: CROSS DATABASE KEY ISSUE</title>
      <link>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876873#M346400</link>
      <description>&lt;P&gt;"Empty" is the same as "missing" for SAS character variables.&lt;/P&gt;
&lt;P&gt;Today, most keys are UUIDs, and you can create such with the&amp;nbsp;&lt;A href="https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/lefunctionsref/n0y09yghr5r11cn1b4ocojwqvrqe.htm" target="_blank" rel="noopener"&gt;UUIDGEN&lt;/A&gt;&amp;nbsp;function; &lt;A href="https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/leforinforref/n115njfuqjerikn1w5g7h5ztwt9m.htm" target="_blank" rel="noopener"&gt;format&lt;/A&gt; them to the readable 36-character notation for the csv file.&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 09:39:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876873#M346400</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2023-05-22T09:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: CROSS DATABASE KEY ISSUE</title>
      <link>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876883#M346402</link>
      <description>&lt;P&gt;If we are talking about strings, yes it could be done this way.&lt;/P&gt;
&lt;P&gt;Remember that the key still needs to be unique.&lt;/P&gt;
&lt;P&gt;I think yuo should take care of your data quality problem first before loading to DB2.&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 11:01:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/CROSS-DATABASE-KEY-ISSUE/m-p/876883#M346402</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2023-05-22T11:01:32Z</dc:date>
    </item>
  </channel>
</rss>

