<?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: Advice on tuning a join/lookup against a very large PostgreSQL table? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Advice-on-tuning-a-join-lookup-against-a-very-large-PostgreSQL/m-p/776384#M246914</link>
    <description>&lt;P&gt;Usually the best way is to upload the SAS table to a temporary table in the database and do the join there with explicit pass through. This minimizes network traffic.&lt;/P&gt;</description>
    <pubDate>Tue, 26 Oct 2021 07:33:02 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2021-10-26T07:33:02Z</dc:date>
    <item>
      <title>Advice on tuning a join/lookup against a very large PostgreSQL table?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Advice-on-tuning-a-join-lookup-against-a-very-large-PostgreSQL/m-p/776377#M246908</link>
      <description>&lt;P&gt;I want to identify all rows in the table SOURCE which don't exist in the table TARGET. This is easily done via this simple code:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;proc sql;
	create table NEW as
	select src.primkey from SOURCE src
	left join TARGET tgt on (src.primkey = tgt.primkey)
	where tgt.primkey is missing;
quit;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;SOURCE is a SAS-table that contains around 3 million rows.&lt;/P&gt;
&lt;P&gt;TARGET is a PostgreSQL-table that contains around &lt;STRONG&gt;750 million rows&lt;/STRONG&gt;. It has an index on primkey.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you know if there's a more efficient way to perform this operation? What's the most optimized way to check if a source row exists in a very large target table?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Oct 2021 06:55:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Advice-on-tuning-a-join-lookup-against-a-very-large-PostgreSQL/m-p/776377#M246908</guid>
      <dc:creator>EinarRoed</dc:creator>
      <dc:date>2021-10-26T06:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: Advice on tuning a join/lookup against a very large PostgreSQL table?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Advice-on-tuning-a-join-lookup-against-a-very-large-PostgreSQL/m-p/776384#M246914</link>
      <description>&lt;P&gt;Usually the best way is to upload the SAS table to a temporary table in the database and do the join there with explicit pass through. This minimizes network traffic.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Oct 2021 07:33:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Advice-on-tuning-a-join-lookup-against-a-very-large-PostgreSQL/m-p/776384#M246914</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2021-10-26T07:33:02Z</dc:date>
    </item>
  </channel>
</rss>

