<?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: Alternative to Interval Match in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856946#M300229</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How many persons are there that need this matching. What is the size of your resulting IntervalMatch extra table(s). What is the span of day that you really need to check against. Are you still using full date as the linking fields in the IntervalMatch? Date could be reduced into a much smaller storage if you are able to limit the scope of the date(s).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 May 2015 08:09:57 GMT</pubDate>
    <dc:creator>petter</dc:creator>
    <dc:date>2015-05-27T08:09:57Z</dc:date>
    <item>
      <title>Alternative to Interval Match</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856944#M300227</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I currently have a model where I am loading in a table detailing where people were based and between what dates. For e.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Name&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Location&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; From&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; To&lt;/P&gt;&lt;P&gt;Bob&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; London&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 01/01/2015&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 31/05/2015&lt;/P&gt;&lt;P&gt;Bob&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; New York&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 01/06/2015&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 31/12/2015&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In another table in my model I am given a particular date and need to find out where that person is based at that time. I've got this working using an interval match function, but the number of records is increasing greatly and it's starting to put quite a drain on the reload time. Is there a better way of doing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2015 07:40:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856944#M300227</guid>
      <dc:creator />
      <dc:date>2015-05-27T07:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Interval Match</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856945#M300228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is your min and max date in your data?&amp;nbsp; - the lowest 'From' and highest 'To' ? If it is then we need to look elsewhere. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure where you are with resident loads and joins but you might be able to link your location mapping table to the main transaction table with an inner join so you only get entries for dates in the transaction table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(The assumption I am making is that you are getting every date between the lowest from to the highest to, in the example above every day between 01/01/2015 and 31/12/2015)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2015 07:52:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856945#M300228</guid>
      <dc:creator>john_s_w_wood</dc:creator>
      <dc:date>2015-05-27T07:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Interval Match</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856946#M300229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How many persons are there that need this matching. What is the size of your resulting IntervalMatch extra table(s). What is the span of day that you really need to check against. Are you still using full date as the linking fields in the IntervalMatch? Date could be reduced into a much smaller storage if you are able to limit the scope of the date(s).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2015 08:09:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/856946#M300229</guid>
      <dc:creator>petter</dc:creator>
      <dc:date>2015-05-27T08:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Alternative to Interval Match</title>
      <link>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/1536614#M439195</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I had the same problem in Qlik Sense,&amp;nbsp;t&lt;SPAN&gt;he size of my resulting IntervalMatch extra table was around 83'000.000 and it crashed. So, I deleted the fields that I didn't need and Loaded Data with a Distinct clause. Thanks for your suggest.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;XOXO&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jan 2019 15:39:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Alternative-to-Interval-Match/m-p/1536614#M439195</guid>
      <dc:creator>karelibarcar</dc:creator>
      <dc:date>2019-01-29T15:39:36Z</dc:date>
    </item>
  </channel>
</rss>

