SAP HANA is an application that utilizes in-memory database innovation that permits the processing of huge amounts of real-time information in a short span. The in-memory figuring engine enables HANA to process information stored in RAM rather than understanding it from a disk. This enables the application to give quick outcomes from client transactions and data analyses. SAP HANA is developed to process organized information from relational databases, both SAP and non-SAP, and applications and different frameworks quickly. It is capable of utilizing three styles of information replication relying upon the source of the information – log-based, ETL-based and trigger-based. The migrated organized information is stored directly in memory. Because of this, information can be gotten to rapidly continuously by the applications that utilize HANA. Initially, HANA was the name given to the new database stage that was discharged by SAP SE. Compared to SAP's before database MaxDB or contenders like Microsoft SQL and Oracle DB, SAP HANA is an in-memory database management framework that claims to be the fastest on the planet for substantial information sizes. To foreground this, SAP holds the World Record for Largest Data Warehouse. Today, SAP HANA is considerably more than only a database platform – it has turned into a foundation of current SAP. Most SAP items can keep running on the HANA database and some are even local HANA and named after the stage itself, similar to S/4 HANA, the successor to the well-known SAP ECC framework. Lately, the database stage and included additional features like application administrations, processing services, and integration services, transforming the stage into an intense device for any association. Does SAP HANA stand to its claim? With our experienced with HANA platform, the response to this question is the undoubtedly yes. We saw various applications where the capacities of the HANA indicated significant guarantee, with the fundamental and most vital one being ‘performance’. Another benefit is that the SAP BI stage is presently profiting by the HANA database, implying that a few information is being read directly from the ECC database, avoiding the change to the SAP BW stage. This enables to report real-time on profitable information. Generally, HANA database has had a discernible effect in the everyday activity of SAP ECC. And what about SAP HANA being costly? While there are license costs you have to pay SAP for the utilization of the HANA database, the costs are customer ward, and comparable to the latest offerings of the contenders. Where things turn out to be marginally more entangled is with respect to the equipment investment you have to make in order to move to or fabricate a HANA certified hardware platform. Since SAP HANA is an in-memory stage, it requires a totally different way to deal with taking a gander at the equipment in the engine of your servers. Getting elite from traditional database stages, for the most part, depends on a fast storage stage and processing power, however with SAP HANA memory is the critical asset. Memory itself is costly, particularly in the event that you are executing large RAM-memory banks, and you will require a server that supports this memory. To minimize expenses, there are servers that support 48 and even up to 96 memory spaces, however even with these, building a strong performing HANA machine will require some investment. So, with new alternatives getting to be accessible, as NVMe storage, later on, the HANA should become more affordable and quicker.