<?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>Question Re: HANA Optimizer function in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaa-p/631558#M156801</link>
    <description>&lt;P&gt;The HANA query optimizer does estimate the memory usage to expect (in terms of records to be expected by the different processing steps) - however using this information alone is insufficient to avoid resource overallocation, which can lead to out of memory errors.&lt;/P&gt;
  &lt;P&gt;No part of a database can predict what the resource allocation will be in the &lt;EM&gt;future&lt;/EM&gt; - that is when your query is being processed - but only how much resources your query &lt;EM&gt;might&lt;/EM&gt; use. HANA can dynamically make memory available, when it needs it and when no other current session requires it. These requirements usually are triggers by components outside of the HANA server, most notably by the database clients.&lt;/P&gt;
  &lt;P&gt;In consequence, this means, it is not generally possible to allow running arbitrary queries against a database and guarantee that there will always be sufficient resources to process them.&lt;/P&gt;
  &lt;P&gt;Having said that, typically it is possible to analyse failing statements and learn the cause(s) for the OOM and to find solutions for them. Very often (in my experience) one can change the query or data model to enable a more memory efficient processing.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 20 May 2018 23:49:16 GMT</pubDate>
    <dc:creator>lbreddemann</dc:creator>
    <dc:date>2018-05-20T23:49:16Z</dc:date>
    <item>
      <title>HANA Optimizer function</title>
      <link>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaq-p/631556</link>
      <description>&lt;P&gt;HI, &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;I'm using SAP HANA DB.&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;There are some problems with user's query. Sometimes it makes OOM on HANA DB. &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;So, i'm thinking of a function that blocks user's query(which may cause OOM) before executing query on HANADB .&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;If SAP HANA optimizer can estimate cost of query user asked, i think that it may possible to forecast that the query may cause OOM or Not. &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;so if SAP HANA optimizer have that kind of function, please tell me how to use it. &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;(If not, also please tell me that it's impossible)&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;thank you for your help &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt;regards, Tae&lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;
  &lt;P&gt; &lt;/P&gt;</description>
      <pubDate>Thu, 17 May 2018 04:49:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaq-p/631556</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2018-05-17T04:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: HANA Optimizer function</title>
      <link>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaa-p/631557#M156800</link>
      <description>&lt;P&gt;Hi Tae,&lt;/P&gt;
  &lt;P&gt;Have you considered Admission Control and/or Workload Management)? &lt;/P&gt;
  &lt;UL&gt;
   &lt;LI&gt;&lt;A href="https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.00/en-US/ab8b81d86d9f43c9b01b299643d56cac.html" target="_blank"&gt;Managing Peak Load (Admission Control)&lt;/A&gt;&lt;/LI&gt;
   &lt;LI&gt;&lt;A href="https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.00/en-US/5066181717df4110931271d1efd84cbc.html" target="_blank"&gt;Managing Workload with Workload Classes&lt;/A&gt;&lt;/LI&gt;
  &lt;/UL&gt;
  &lt;P&gt;Regards,&lt;/P&gt;
  &lt;P&gt;Denys / SAP HANA Academy&lt;/P&gt;</description>
      <pubDate>Fri, 18 May 2018 08:58:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaa-p/631557#M156800</guid>
      <dc:creator>dvankempen</dc:creator>
      <dc:date>2018-05-18T08:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: HANA Optimizer function</title>
      <link>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaa-p/631558#M156801</link>
      <description>&lt;P&gt;The HANA query optimizer does estimate the memory usage to expect (in terms of records to be expected by the different processing steps) - however using this information alone is insufficient to avoid resource overallocation, which can lead to out of memory errors.&lt;/P&gt;
  &lt;P&gt;No part of a database can predict what the resource allocation will be in the &lt;EM&gt;future&lt;/EM&gt; - that is when your query is being processed - but only how much resources your query &lt;EM&gt;might&lt;/EM&gt; use. HANA can dynamically make memory available, when it needs it and when no other current session requires it. These requirements usually are triggers by components outside of the HANA server, most notably by the database clients.&lt;/P&gt;
  &lt;P&gt;In consequence, this means, it is not generally possible to allow running arbitrary queries against a database and guarantee that there will always be sufficient resources to process them.&lt;/P&gt;
  &lt;P&gt;Having said that, typically it is possible to analyse failing statements and learn the cause(s) for the OOM and to find solutions for them. Very often (in my experience) one can change the query or data model to enable a more memory efficient processing.&lt;/P&gt;
  &lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 20 May 2018 23:49:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/hana-optimizer-function/qaa-p/631558#M156801</guid>
      <dc:creator>lbreddemann</dc:creator>
      <dc:date>2018-05-20T23:49:16Z</dc:date>
    </item>
  </channel>
</rss>

