<?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: SAP Datasphere ROW ENGINE issues in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808782#M4809915</link>
    <description>&lt;P&gt;Great to hear.&lt;/P&gt;</description>
    <pubDate>Mon, 31 Jul 2023 11:43:29 GMT</pubDate>
    <dc:creator>Dominik7727</dc:creator>
    <dc:date>2023-07-31T11:43:29Z</dc:date>
    <item>
      <title>SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaq-p/12808777</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
  &lt;P&gt;sometimes for &lt;STRONG&gt;&lt;U&gt;SIMPLE&lt;/U&gt;&lt;/STRONG&gt; calculations in graphical views we experience OOM issues.&lt;/P&gt;
  &lt;P&gt;How this happens:&lt;/P&gt;
  &lt;P&gt;consider this calculated column:&lt;/P&gt;
  &lt;P&gt;TO_DATE( TO_VARCHAR( SALESDOCUMENTDATE, 'YYYY') || '0101', 'YYYYMMDD').&lt;/P&gt;
  &lt;P&gt;This will trigger a temporary ROW STORE materialization visible in explain plan.&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2184999-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;if I remove the calculated column : no ROW SEARCH step appear:&lt;/P&gt;
  &lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/2185000-image.png" /&gt;&lt;/P&gt;
  &lt;P&gt;This do not affect too much performances in case of few columns many rows.&lt;/P&gt;
  &lt;P&gt;In case of many columns and few rows ( like 300+ columns available in SD standard BI Content made by SAP ).&lt;/P&gt;
  &lt;P&gt;&lt;U&gt;We experience a x100 factor in memory usage during View persistency, and partitioning do not help too much.&lt;/U&gt;&lt;/P&gt;
  &lt;P&gt;So for ~ 4 Million rows times ~ 300 columns we hit over 20GB of memory during execution.&lt;/P&gt;
  &lt;P&gt;While the persisted View account only for 200MB.&lt;/P&gt;
  &lt;P&gt;This do not ends here, &lt;/P&gt;
  &lt;P&gt;if the views are used by third party BI tools (with 1 daily full import to the other BI tool, so a "select *" statement is issued ),&lt;/P&gt;
  &lt;P&gt;Just adding a simple calculation as shown above will trigger OOM issues.&lt;/P&gt;
  &lt;P&gt;This issues are not visible during modelling and MAY involve colleagues from other teams (sys admins), to analyze in hana cockpit / SQL console. This is a real big issues as in big projects 30% of the time is spent in this kind of optimization ( that we can call "bug hunting" ).&lt;/P&gt;
  &lt;P&gt;I have 2 questions:&lt;/P&gt;
  &lt;P&gt;1) When Row Engine will be completely removed in favour of ESX ?&lt;/P&gt;
  &lt;P&gt;2) Is there a way to know which function available in graphical view editor will trigger a row store temporary materialization ? ( can someone add a sort of "black pirate flag" to spot this ? ).&lt;/P&gt;
  &lt;P&gt;Best Regards,&lt;/P&gt;
  &lt;P&gt;Alberto&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 16:57:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaq-p/12808777</guid>
      <dc:creator>albertosimeoni</dc:creator>
      <dc:date>2023-07-25T16:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808778#M4809911</link>
      <description>&lt;P&gt;HI Alberto,&lt;/P&gt;&lt;P&gt;Are you added calculated column at very bottom of your view?&lt;/P&gt;&lt;P&gt;Have tried to force engine with hints?&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.sap.com/docs/SAP_HANA_PLATFORM/9de0171a6027400bb3b9bee385222eff/a1664ad72db542d9a519d1e195a02d37.html" target="test_blank"&gt;https://help.sap.com/docs/SAP_HANA_PLATFORM/9de0171a6027400bb3b9bee385222eff/a1664ad72db542d9a519d1e195a02d37.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Dominik&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 14:50:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808778#M4809911</guid>
      <dc:creator>Dominik7727</dc:creator>
      <dc:date>2023-07-26T14:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808779#M4809912</link>
      <description>&lt;P&gt;Hello Dominik,&lt;/P&gt;&lt;P&gt;the HANA cloud database in my case is managed by the application (SAP Datasphere), &lt;/P&gt;&lt;P&gt;So I have not a user/login with privileges to change configuration parameters.&lt;/P&gt;&lt;P&gt;The procedure to persist a view is triggered and managed by the application, so I can not enter an execution hint on it.&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Alberto&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2023 15:18:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808779#M4809912</guid>
      <dc:creator>albertosimeoni</dc:creator>
      <dc:date>2023-07-26T15:18:51Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808780#M4809913</link>
      <description>&lt;P&gt;Beauty of cloud solutions.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 07:05:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808780#M4809913</guid>
      <dc:creator>Dominik7727</dc:creator>
      <dc:date>2023-07-27T07:05:55Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808781#M4809914</link>
      <description>&lt;P&gt;We partially solved problems of third party BI Client Using&lt;/P&gt;&lt;P&gt;"WITH HINT(USE_HEX_PLAN)"&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 10:12:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808781#M4809914</guid>
      <dc:creator>albertosimeoni</dc:creator>
      <dc:date>2023-07-31T10:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: SAP Datasphere ROW ENGINE issues</title>
      <link>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808782#M4809915</link>
      <description>&lt;P&gt;Great to hear.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 11:43:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/sap-datasphere-row-engine-issues/qaa-p/12808782#M4809915</guid>
      <dc:creator>Dominik7727</dc:creator>
      <dc:date>2023-07-31T11:43:29Z</dc:date>
    </item>
  </channel>
</rss>

