<?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: Joining on Nearest Timestamp in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797485#M313517</link>
    <description>&lt;P&gt;See if you can use this as an example. Should scale well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data one;
input id n1;
datalines;
1 3.4 
1 7.9 
1 6.1 
2 4.7 
2 9.2 
3 6.3 
3 1.1 
3 8.3 
;
 
proc plan;
   factors id = 3 n2 = 5 / noprint;
   output out=two;
run;quit;

data want(keep = id n2 closest);
   if _N_ = 1 then do;
      if 0 then set one;
      dcl hash h(dataset : "one(rename = (id = _id)", ordered : "Y");
      h.definekey("_id", "n1");
      h.definedone();
      dcl hiter i("h");
   end;
 
   set two;
   _id = .;
 
   if h.check(key : id, key : n2) = 0 then closest = n2;
 
   else do;
      h.add(key : id, key : n2, data : id, data : n2);
 
      if i.setcur(key : id, key : n2) = 0 then
         if i.prev() = 0 &amp;amp; id = _id then pn1 = n1;
 
      if i.setcur(key : id, key : n2) = 0 then
         if i.next() = 0 &amp;amp; id = _id then nn1 = n1;
 
      if      nn1 = . then idx = 1;
      else if pn1 = . then idx = 2;
      else idx = 1 + (n2 - pn1 &amp;gt; nn1 - n2);
 
      closest = choosen(idx, pn1, nn1);
 
      h.remove(key : id, key : n2);
   end;
run;&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Sun, 20 Feb 2022 18:47:36 GMT</pubDate>
    <dc:creator>PeterClemmensen</dc:creator>
    <dc:date>2022-02-20T18:47:36Z</dc:date>
    <item>
      <title>Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797478#M303177</link>
      <description>&lt;P&gt;I have 2 datasets that I have to join based on same account key and nearest timestamp from same date to obtain the transaction ID from the larger dataset. Table A only has about a million records, but Table B has 1.5 billion. I've attempted the below code format and error out due to inadequate session memory. This occurs even if I invoke max MEMSIZE at session launch. There are multiple instances of timestamps per account and the timestamps are off by a few seconds between each dataset, so I can't do an exact join on account and timestamps. Is there a more efficient way to accomplish this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;proc sql;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;create table timematch&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;as select a*, b.transactionid&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;, a.datetime - b.datetime as seconds&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;, abs(calculated seconds) as distance&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;from tablea a&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp;left join tableb b&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp;on a.account=b.account&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp; &amp;nbsp;and a.date=datepart(b.datetime)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;group by a.account, a.date, a.datetime&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;having min(calculated distance) = calculated distance;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;quit;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 20 Feb 2022 16:31:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797478#M303177</guid>
      <dc:creator>lujo1017</dc:creator>
      <dc:date>2022-02-20T16:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797483#M313515</link>
      <description>&lt;P&gt;There is probably a better way that will increase performance and save time. Are you able to post some example data that resembles your actual data?&lt;/P&gt;</description>
      <pubDate>Sun, 20 Feb 2022 18:18:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797483#M313515</guid>
      <dc:creator>PeterClemmensen</dc:creator>
      <dc:date>2022-02-20T18:18:57Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797485#M313517</link>
      <description>&lt;P&gt;See if you can use this as an example. Should scale well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data one;
input id n1;
datalines;
1 3.4 
1 7.9 
1 6.1 
2 4.7 
2 9.2 
3 6.3 
3 1.1 
3 8.3 
;
 
proc plan;
   factors id = 3 n2 = 5 / noprint;
   output out=two;
run;quit;

data want(keep = id n2 closest);
   if _N_ = 1 then do;
      if 0 then set one;
      dcl hash h(dataset : "one(rename = (id = _id)", ordered : "Y");
      h.definekey("_id", "n1");
      h.definedone();
      dcl hiter i("h");
   end;
 
   set two;
   _id = .;
 
   if h.check(key : id, key : n2) = 0 then closest = n2;
 
   else do;
      h.add(key : id, key : n2, data : id, data : n2);
 
      if i.setcur(key : id, key : n2) = 0 then
         if i.prev() = 0 &amp;amp; id = _id then pn1 = n1;
 
      if i.setcur(key : id, key : n2) = 0 then
         if i.next() = 0 &amp;amp; id = _id then nn1 = n1;
 
      if      nn1 = . then idx = 1;
      else if pn1 = . then idx = 2;
      else idx = 1 + (n2 - pn1 &amp;gt; nn1 - n2);
 
      closest = choosen(idx, pn1, nn1);
 
      h.remove(key : id, key : n2);
   end;
run;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 20 Feb 2022 18:47:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797485#M313517</guid>
      <dc:creator>PeterClemmensen</dc:creator>
      <dc:date>2022-02-20T18:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797488#M313520</link>
      <description>&lt;P&gt;Below are a few sample records from each table. Transaction_Amts between the 2 datasets do not line up due to conversion rates and other factors in creation of the data in table A. Timestamps may be off&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Table A Sample:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="1" cellspacing="0" cellpadding="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;ACCOUNT_ID&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;TRANSACTION_DATE&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;DATE_TIME&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;TRANSACTION_AMT&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;0000165033E8A3EFC15&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;06/12/2021&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;06Dec2021 22:57:42&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;1,599.00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;00005D318BCCCE8AA93&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;23/12/2021&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;23Dec2021 18:54:00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;1.00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;0000653BAA33A87F242&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30/10/2021&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Oct2021 14:27:00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;14.90&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;00009F79D3AC781E7EE&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;19/09/2021&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;19Sep2021 18:04:58&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30.00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;00009F79D3AC781E7EE&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;19/09/2021&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;19Sep2021 18:05:58&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30.00&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Table B Sample&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="1" cellspacing="0" cellpadding="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;TRANSACTION_DTTM&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;TRANSACTION_ID &lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;ACCOUNT_ID &lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;TRANSACTION_AMT&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;6c6103ef9b044e1c&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;465EE79A6412B62C825&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;046103ef98044df9&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;77987B571FCF27B5633&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;686103ee4404491c&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;A16EF924DB414AB3D3F&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;17.9&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;006103ef98044b13&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;1B4EE07C3778C8CB03A&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;0.78&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;64610435d3027617&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;22CFD191C879FE130EF&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;0.38&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:16&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;6c6103ef9b044e1d&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;1747E9B180376F04F72&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:10&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;386103eea4044cbe&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;1F1EF0192FB7F1C8317&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;1.26&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;30Jul2021 21:00:10&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;6c6103ef9b044dfd&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;&lt;SPAN&gt;F494EED4074847E41A8&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD&gt;&lt;P align="right"&gt;&lt;SPAN&gt;180.19&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Sun, 20 Feb 2022 19:07:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797488#M313520</guid>
      <dc:creator>lujo1017</dc:creator>
      <dc:date>2022-02-20T19:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797489#M313521</link>
      <description>&lt;P&gt;I would suggest that you select a max value of time stamp difference and modify your query as follows.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;%let tolerance = ;/* select the value you can tolerate*/
proc sql; 
create table timematch as
 select a*, b.transactionid,
abs( timepart(a.datetime) - timepart(b.datetime) ) as distance
from table a  left join table b 
on a.account=b.account
and datepart(a.datetime)=datepart(b.datetime)
group by a.account, a.date, a.datetime
having calculated distance) le &amp;amp;tolerance;
quit;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 21 Feb 2022 02:54:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797489#M313521</guid>
      <dc:creator>Sajid01</dc:creator>
      <dc:date>2022-02-21T02:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797491#M313523</link>
      <description>&lt;P&gt;Can you put these in a datastep code?&lt;/P&gt;</description>
      <pubDate>Sun, 20 Feb 2022 19:32:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797491#M313523</guid>
      <dc:creator>Sajid01</dc:creator>
      <dc:date>2022-02-20T19:32:15Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797494#M313525</link>
      <description>&lt;P&gt;So what does your desired result look like given this data?&lt;/P&gt;</description>
      <pubDate>Sun, 20 Feb 2022 20:13:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797494#M313525</guid>
      <dc:creator>PeterClemmensen</dc:creator>
      <dc:date>2022-02-20T20:13:50Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797495#M313526</link>
      <description>&lt;P&gt;I'd like a table of everything from Table A, plus the transaction ID from table B that matches on account ID and date exactly, with closest match on timestamp. Amounts are unreliable, so they're not very useful to me in joining.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 20 Feb 2022 20:33:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797495#M313526</guid>
      <dc:creator>lujo1017</dc:creator>
      <dc:date>2022-02-20T20:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: Joining on Nearest Timestamp</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797526#M313547</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/417491"&gt;@lujo1017&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;The account_id's in the two tables you have posted are different.&lt;BR /&gt;Therefore the joined data set will only have data from the left table.&lt;BR /&gt;Please put a representative data as a sas datastep and make sure the datasets have some rows which fulfill the join condition.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 03:14:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Joining-on-Nearest-Timestamp/m-p/797526#M313547</guid>
      <dc:creator>Sajid01</dc:creator>
      <dc:date>2022-02-21T03:14:37Z</dc:date>
    </item>
  </channel>
</rss>

