Scribd Logo
Upload

Welcome to Scribd!

  • 2K views

    Telc Deutsch A1 Uebungstest 1

    Uploaded by

    saikiranvaddi
    The main factors for sizing a SAP HANA system's memory are the size of the table data and additional working memory required, which is typically similar in size to the table data. Memory is also needed for code, caches, and operating system files, though these areas are generally much smaller than the database areas. For SAP S/4HANA scale-out sizing, the landscape consists of a master node and up to 3 slave nodes, with tables grouped and located on nodes based on predefined or custom groups, and nodes can have uneven memory usage.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Telc Deutsch A1 Uebungstest 1

    Uploaded by

    saikiranvaddi
    2K views1 page
    The main factors for sizing a SAP HANA system's memory are the size of the table data and additional working memory required, which is typically similar in size to the table data. Memory is also needed for code, caches, and operating system files, though these areas are generally much smaller than the database areas. For SAP S/4HANA scale-out sizing, the landscape consists of a master node and up to 3 slave nodes, with tables grouped and located on nodes based on predefined or custom groups, and nodes can have uneven memory usage.

    Original Description:

    size s4

    Original Title

    Telc Deutsch a1 Uebungstest 1

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The main factors for sizing a SAP HANA system's memory are the size of the table data and additional working memory required, which is typically similar in size to the table data. Memory is also needed for code, caches, and operating system files, though these areas are generally much smaller than the database areas. For SAP S/4HANA scale-out sizing, the landscape consists of a master node and up to 3 slave nodes, with tables grouped and located on nodes based on predefined or custom groups, and nodes can have uneven memory usage.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    2K views1 page

    Telc Deutsch A1 Uebungstest 1

    Uploaded by

    saikiranvaddi
    The main factors for sizing a SAP HANA system's memory are the size of the table data and additional working memory required, which is typically similar in size to the table data. Memory is also needed for code, caches, and operating system files, though these areas are generally much smaller than the database areas. For SAP S/4HANA scale-out sizing, the landscape consists of a master node and up to 3 slave nodes, with tables grouped and located on nodes based on predefined or custom groups, and nodes can have uneven memory usage.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 1

    The main driver for memory sizing is the table data of the planned

    SAP HANA system


    Most tables are in the highly compressed column store of SAP
    HANA
    For working memory of the database and temporary calculations,
    almost the same size as for table data is required additionally

    A SAP HANA database includes further memory areas, such as code,
    stack, caches, operating system and other system files. These areas
    are typically small compared to a typical database

    100 SAPS = 2,000 fully processed order line items per hour

    The important concepts for SAP S/4HANA scale-out sizing are as


    follows:
    The scale-out landscape consists of one master node and up to 3
    slaves.
    Tables are grouped in-predefined groups delivered by SAP and in
    custom-defined groups.
    All of the tables in one group are located on the same server node.
    Only tables in a group can be moved to a slave node. All other
    tables remain on the master node.
    Nodes can have uneven memory use.

    You might also like