T-shirt sizes for SAP HANA


T-shirt sizes for SAP HANA

SAP defined so-called T-shirt sizes for SAP HANA to both simplify the sizing and to limit the
number of hardware configurations to support, thus reducing complexity. SAP’s hardware
partners provide configurations for SAP HANA according to one or more of these T-shirt sizes.



In addition to the T-shirt sizes listed in Table, you might come across the T-shirt size XL,
which denotes a scale-out configuration for SAP HANA.
The T-shirt sizes S+ and M+ denote upgradable versions of the S and M sizes:
S+ delivers capacity equivalent to S, but the hardware is upgradable to an M size.
M+ delivers capacity equivalent to M, but the hardware is upgradable to an L size.

These T-shirt sizes are used when relevant growth of the data size is expected.


For information about RAM sizing :

Sizing the RAM for SAP HANA

Comments

Post a Comment

Popular posts from this blog

SAP HANA Introduction

Image
SAP HANA:The future of database technology The capacity of main memory in servers has continuously increased over the years, whereas prices have dramatically dropped. Today, a single enterprise class server can hold several  terabytes of main memory. At the same time, prices for server main memory dramatically  dropped over the last few decades. This increase in capacity and reduction in cost makes it a  viable approach to keep huge amounts of business data in memory. This section discusses  the benefits and challenges. In few words you can understand SAP HANA plus  analyzing this evaluation: Typical access speeds Disk     4,000,000 ns Memory         0.4 ns Speed   10,000,000 Falling prices move processing from Disk/SSD to In-Memory In-Memory Computing The elements of In-Memory computing are not new. However, dramatically improved hardware economics and  technology innovations in software has now made it possible for SAP to deliver on its vision of the
Read more

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-NL0CYP13VZ"></script> <script>   window.dataLayer = window.dataLayer || [];   function gtag(){dataLayer.push(arguments);}   gtag('js', new Date());   gtag('config', 'G-NL0CYP13VZ'); </script> Cannot find the BusinessObjects Enterprise report source. (LO 26608) Environment SAP BO XI 4.1 SP 5 two nodes Cluster Windows Server 2012 While refreshing dashboard (based on Live Office connection) from BI Launchpad with a no administrator user the above exception was erased. SAP says: Cause The document is not available; for example it does not exist, or it has been removed. Action Check the report path from CMS and use SetLocation in Live Office to re-define the report source. Otherwise, check if the user has sufficient rights to view the object. Solution In our case  we fixed this problem was to remo
Read more

FWM 01002 - Unable to reconnect to the CMS. The session has been logged off or has expired.

An error has occurred: Unable to reconnect to the CMS.  The session has been logged off or has expired. (FWM 01002) Environment BO XI R 3.1 SP 4 In order to solve this issue we found a  SAP released note 1422296  1422296 - Error:' Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' with BusinessObjects XI 3.1. Symptom Not able to schedule WebIntelligence reports. Reports fail with error:'Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Environment BusinessObjects XI 3.1. Reproducing the Issue Schedule a WebIntelligence report to run now. Reports fails with error:u2018Unable to reconnect to CMS :6400. The session has been logged off or has expired.(FWM 01002)' Resolution 1. From Central Configuration Manager, disable all the services and re-enable them. 2. Log into Central Management Console and go to the server area. 3. Go to the properties of Central Man
Read more