<?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 Easy in Qlik Script but hard in SQL in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Easy-in-Qlik-Script-but-hard-in-SQL/m-p/1371557#M616349</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have read that there are things that are easy to do in Qlik Script but hard to do in SQL (&lt;A href="https://community.qlikview.com/thread/132601" title="https://community.qlikview.com/thread/132601"&gt;ETL: Qlik Scripting vs Sql query | Qlik Community&lt;/A&gt;).&amp;nbsp; Does anyone have good examples of this?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been working with Qlik for a while, but have less experience with SQL and am curious as to how they compare.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Jun 2017 21:50:49 GMT</pubDate>
    <dc:creator>reanfadyl</dc:creator>
    <dc:date>2017-06-14T21:50:49Z</dc:date>
    <item>
      <title>Easy in Qlik Script but hard in SQL</title>
      <link>https://community.qlik.com/t5/QlikView/Easy-in-Qlik-Script-but-hard-in-SQL/m-p/1371557#M616349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have read that there are things that are easy to do in Qlik Script but hard to do in SQL (&lt;A href="https://community.qlikview.com/thread/132601" title="https://community.qlikview.com/thread/132601"&gt;ETL: Qlik Scripting vs Sql query | Qlik Community&lt;/A&gt;).&amp;nbsp; Does anyone have good examples of this?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been working with Qlik for a while, but have less experience with SQL and am curious as to how they compare.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rean&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 21:50:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Easy-in-Qlik-Script-but-hard-in-SQL/m-p/1371557#M616349</guid>
      <dc:creator>reanfadyl</dc:creator>
      <dc:date>2017-06-14T21:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: Easy in Qlik Script but hard in SQL</title>
      <link>https://community.qlik.com/t5/QlikView/Easy-in-Qlik-Script-but-hard-in-SQL/m-p/1371558#M616350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Qlik Script has a number of features designed to server the specialized requirements of Qlik Transformation and Dimensional Modeling. A few things that come to mind that are easy in Qlik but harder in SQL:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. MAPPING.&amp;nbsp; Whether data mapping or "RENAME FIELDS USING mapname" the Qlik solution is simple and elegant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. IntervalMatch.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Qlik Script provides more Datetime functions than a typical SQL implementation. For example, "InYearToDate()".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Rob&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://masterssummit.com/" rel="nofollow" target="_blank"&gt;http://masterssummit.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://qlikviewcookbook.com/" rel="nofollow" target="_blank"&gt;http://qlikviewcookbook.com&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Jun 2017 22:58:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Easy-in-Qlik-Script-but-hard-in-SQL/m-p/1371558#M616350</guid>
      <dc:creator>rwunderlich</dc:creator>
      <dc:date>2017-06-14T22:58:28Z</dc:date>
    </item>
  </channel>
</rss>

