<?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: Optimizing Data Processing for UI Migration from SAP... in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/optimizing-data-processing-for-ui-migration-from-sap-netweaver-to-btp-cloud/qaa-p/13875812#M4885272</link>
    <description>&lt;P&gt;May using SAP HANA Smart Data Access (SDA) or Smart Data Integration (SDI) to create virtual tables in your HANA Cloud DB linked to your On-Premise DB. If this works fine, that could allow data processing directly on your On-Premise DB without replication, but may have its own challenges.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Sep 2024 11:03:04 GMT</pubDate>
    <dc:creator>HakanHaslaman</dc:creator>
    <dc:date>2024-09-24T11:03:04Z</dc:date>
    <item>
      <title>Optimizing Data Processing for UI Migration from SAP NetWeaver to BTP Cloud Foundry</title>
      <link>https://community.sap.com/t5/technology-q-a/optimizing-data-processing-for-ui-migration-from-sap-netweaver-to-btp-cloud/qaq-p/13871058</link>
      <description>&lt;P&gt;There is UI Migration going exchange the current UI from SAP Netweaver to BTP Cloud Foundry without switching databases.&lt;/P&gt;&lt;P&gt;Presently, data is replicated from CRM to our On-Premise DB via SLT and from On-Premise DB it is getting replicated to HANA Cloud DB. We have also created Virtual tables in HANA Cloud DB.&lt;/P&gt;&lt;P&gt;The users are using SAP Netweaver to download the data and processing (SELECT, JOINS, etc) takes place when users initiate a download from On-Prem DB.&lt;/P&gt;&lt;P&gt;Users are now working on an Application and HDI which is querying the replicated&amp;nbsp;Virtual tables in HANA Cloud DB. This is consuming all memory from HANA Cloud DB.&lt;/P&gt;&lt;P&gt;Hence, we have a requirement from DB side where the ask is to exclude the use HANA Cloud DB from processing any queries (as we get memory issues due to big tables) and ensuring all data processing happens directly within On-Premise DB instead of&amp;nbsp;HANA Cloud DB.&lt;/P&gt;&lt;P&gt;Since the data is Day Based, we are thinking for creating views using filters like&amp;nbsp;country or region in On-Premise Database and replicating these views on HANA Cloud such that&amp;nbsp;data will be pre-processed and ready for download for users, removing the need for any processing at the time the user clicks download.&lt;/P&gt;&lt;P&gt;Could anyone kindly let us know if this is approach is good and can be done. If not, we are open to suggestion if it can be done in any other better way. Please help!..&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 12:46:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/optimizing-data-processing-for-ui-migration-from-sap-netweaver-to-btp-cloud/qaq-p/13871058</guid>
      <dc:creator>KarthikKumar31</dc:creator>
      <dc:date>2024-09-19T12:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Optimizing Data Processing for UI Migration from SAP...</title>
      <link>https://community.sap.com/t5/technology-q-a/optimizing-data-processing-for-ui-migration-from-sap-netweaver-to-btp-cloud/qaa-p/13875812#M4885272</link>
      <description>&lt;P&gt;May using SAP HANA Smart Data Access (SDA) or Smart Data Integration (SDI) to create virtual tables in your HANA Cloud DB linked to your On-Premise DB. If this works fine, that could allow data processing directly on your On-Premise DB without replication, but may have its own challenges.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 11:03:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/optimizing-data-processing-for-ui-migration-from-sap-netweaver-to-btp-cloud/qaa-p/13875812#M4885272</guid>
      <dc:creator>HakanHaslaman</dc:creator>
      <dc:date>2024-09-24T11:03:04Z</dc:date>
    </item>
  </channel>
</rss>

