<?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: DI Studio SCD Type 1 table loader in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/DI-Studio-SCD-Type-1-table-loader/m-p/158551#M30973</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sounds like a heck of time for so little records, independent of update technique.&lt;/P&gt;&lt;P&gt;And yes, there are stuff you can do to optimize the code.&lt;/P&gt;&lt;P&gt;But first things first. Locate in the log the step(s) that consumes the most resources, and try to start from there.&lt;/P&gt;&lt;P&gt;What aboit other processing - is this the only job that performs poor? Or coudl it be a system constraint?&lt;/P&gt;&lt;P&gt;Why are you using the Type 1 Loader? I seldom use it. Depending on your requirement you could use a standard Table Loader, or the Type 2 Loader.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Feb 2014 08:55:16 GMT</pubDate>
    <dc:creator>LinusH</dc:creator>
    <dc:date>2014-02-01T08:55:16Z</dc:date>
    <item>
      <title>DI Studio SCD Type 1 table loader</title>
      <link>https://communities.sas.com/t5/SAS-Programming/DI-Studio-SCD-Type-1-table-loader/m-p/158550#M30972</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 am trying to utilise the type 1 table loader so I can update a table with only changed dimensions.&amp;nbsp; The table has 70k rows and 5 variables.&amp;nbsp; I require 3 varibale s as my lookup to check for any change and then I have one target column that is changed.&amp;nbsp; This is the first time I have&amp;nbsp; used the a SCD and I am finding it can take up to 15 miutes to run with potentially only 3k records changing.&amp;nbsp; Firstly is this normal? Secondly how can I optimise this time?&amp;nbsp; I have experimented with different hash lookup sizes and no noticeable improvement is made.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Jan 2014 17:04:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/DI-Studio-SCD-Type-1-table-loader/m-p/158550#M30972</guid>
      <dc:creator>qwererty</dc:creator>
      <dc:date>2014-01-31T17:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: DI Studio SCD Type 1 table loader</title>
      <link>https://communities.sas.com/t5/SAS-Programming/DI-Studio-SCD-Type-1-table-loader/m-p/158551#M30973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sounds like a heck of time for so little records, independent of update technique.&lt;/P&gt;&lt;P&gt;And yes, there are stuff you can do to optimize the code.&lt;/P&gt;&lt;P&gt;But first things first. Locate in the log the step(s) that consumes the most resources, and try to start from there.&lt;/P&gt;&lt;P&gt;What aboit other processing - is this the only job that performs poor? Or coudl it be a system constraint?&lt;/P&gt;&lt;P&gt;Why are you using the Type 1 Loader? I seldom use it. Depending on your requirement you could use a standard Table Loader, or the Type 2 Loader.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Feb 2014 08:55:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/DI-Studio-SCD-Type-1-table-loader/m-p/158551#M30973</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2014-02-01T08:55:16Z</dc:date>
    </item>
  </channel>
</rss>

