Compare SAP HANA vs. SQL Server

SAP HANA is ranked 7th in Relational Databases with 1 review while SQL Server which is ranked 1st in Relational Databases with 21 reviews. SAP HANA is rated 10.0, while SQL Server is rated 10.0. The top reviewer of SAP HANA writes "Provides us with predictive capabilities for asset maintenance, and real-time forecasts". On the other hand, the top reviewer of SQL Server writes "Enabled us to use an Agile approach to the design and implementation of DW solutions". SAP HANA is most compared with SQL Server, Oracle Database In-Memory and Oracle Database, whereas SQL Server is most compared with Oracle Database, SAP HANA and Teradata.
Cancel
You must select at least 2 products to compare!
SAP HANA Logo
12,968 views|7,709 comparisons
SQL Server Logo
30,516 views|16,936 comparisons
Most Helpful Review
Find out what your peers are saying about Microsoft, Oracle, Teradata and others in Relational Databases. Updated: July 2019.
354,290 professionals have used our research since 2012.
Quotes From Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:

Pros
Provides us with predictive capabilities for asset maintenance, and real-time forecasts.

Read more »

It is one of the most stable relational databases out there.I have experience with this product for many years. I never have problems with it. It can handle a PC, and it can also handle huge data. It is fast and efficient.This solution has proven stability and operational power.Tuning Advisor suggests where to add indexes and from where to remove them. It works like an adviser.SQL Server Profiler makes finding and debugging easy.I use it to fine tune my procedures and functions.Enables us to convert to bigger DBs and more easily move or upgrade between branches.Without any doubt the Integration Services and Analysis Services are the most widely used. These are the basis for data quality, data gathering, ETL process, as well as collation for the data warehouse, Cube-generation, and ad-hoc processes. The ease in which you may mold a process flow or even modularly add in new structures is something which is much needed in my job.

Read more »

Cons
Needs graphical programming without coding.

Read more »

I would like to see native plugins built for other platforms versus having to buy third-party plugins to tap into S3 buckets and AWS Cloud. Right now, it does not have those built-in plugins.It would be nice if there was a feature to search for a specific value across multiple tables. This would save a lot of time for its users.Improvements to the indexing, columnstore indexing, and high availability groups are good improvements for future versions.Third-party services from Redgate should be built-in to it, like SQL Search.Debugging from the debugger tool functionality should be enhanced.From a DB administrator perspective, I would like to see more space requirements and space capacity history, so that we are able to see which DBs are growing, and by how much per day or week.An area for improvement would be the SQL Server process monitoring, which is quite basic and could sustain more information.The only item which I can list is application failure during Integration Services debugging, when restarting a process flow. In a number of instances the solutions fails. I have not given this much thought and simply stop and start the debugging service rather than restarting.

Read more »

Pricing and Cost Advice
Set up a consortium of consulting partners and hardware vendors to define your tech. Landscape TCO (total cost of ownership) and then approach the OEM for pricing (on-premise or on cloud or a hybrid model). Check if you can bring your own licenses for some of the existing application licenses on the new platform, to reduce TCO.

Read more »

It is expensive, but you get what you pay for.Since we are a cloud-based company, there is AWS pricing on top of the SQL Server pricing. The Enterprise Edition can typically sell from around $1000 dollars a month, which is not cheap. Then, there is an additional one-time Windows cost, based on the code, which can go anywhere from $30,000 to $40,000 for the license.The setup cost is high, but it will return every penny.My advice is quite straightforward. If you know the number of users who really and truly need access to the Server then it is a no-brainer. If you do not know, then get the basic package and minimum licenses and start from there. Needless to say, users can develop/use data structures outside and then deploy onto the Server.The price has been going higher and higher. The market is quite price sensitive.This is a downside of enterprise Microsoft products.Currently, almost all of my machines are in Azure and I think it is the best way of licensing now (VM+software).​We are a Microsoft shop, so we use Active Directory. That integrates well with this product, but we did look at Oracle. We also looked at IBM. This was the best price point for us for what we were getting.​

Read more »

report
Use our free recommendation engine to learn which Relational Databases solutions are best for your needs.
354,290 professionals have used our research since 2012.
Answers from the Community
Rhea Rapps
Bonnie HarmonUser

I agree with the two statements below and would add:

MS SQL Server:

Pros:

* Large base of experienced users and knowledge base
* Can be installed on most Linux or Windows operating systems
* Favorable dollar investment (compared to HANA)
* Managed through SQL Server Management Studio, a well-known tool

Cons:

* No direct ties to SAP ECC
* Limited analytics in standard setup
* Would need to install Analysis Services for increased analytics tools, if analysis is desired.
* Row oriented design impacts performance for large searches.
* SQL trying to catch up to in-memory, and column oriented

SAP HANA:

Pros:

* One tool for standard DB (OLTP) functionality as well as analysis
* Fast. (Although the speed differences are reported most dramatics with the analytics side)
* Real-time analytics
* SQL language
* Column design improves data warehouse performance

Cons:

* Limited pool of experienced users with a small knowledge base (newer product)
* More expensive
* Limited installation options: cloud service or as appliance
* Managed through HANA tools - little known
* Column-oriented unfamiliar to SQL developers trying to

Both are relational databases. Being a long-time SQL user, I am comfortable with its limitations. But as I am exposed more to HANA, it truly is the preferred way to achieve real-time integration and analytics with SAP. When it becomes more cost effective, I think the switch will become more frequent to HANA.

30 May 19
Bruce GreeffReal User

The two are not really directly comparable. HANA DB is designed to run in-memory. It indexes every attribute and converts values to integer, offering real time performance. SQL Server is a more general purpose, inherently relational product. Depending on use case - either may be better. HANA is entirely next generation. SQL Server has to maintain legacy compatibility - but it is easier to use and you can scale the infrastructure cost down. HANA is designed for appliance deployment. Scaling is expensive. To get similar capabilities to HANA you might have to add something like SPARK and /or REDIS to your SQL Server. Then it starts getting expensive and complex too.

26 July 18
Joe FernandesReal User

SAP HANA runs queries "In Memory". Results of a query on large data volumes will appear lighting quick as a result. SQL Server is not an "In Memory" database. It is better suited while accessing smaller data volumes.

26 July 18
JanisGriffinReal User

I think I would prefer SQL Server over HANA because it's been around longer and is more well known. Also, the later versions of SQL Server allow for in memory column store, faster analytical queries and plays well with open source solutions.

25 July 18
Evan HaxtonVendor

A lot depends upon what application is running on top of the data store.

If you are running SAP Business One, a compelling argument is made here
<https://www.afon.com.sg/blog/know-your-software-sap-business-one-on-hana-vs.-mssql>.
Essentially, SAP HANA (SAPH) offers in-memory processing and should be
faster in most cases.
However, if you are running SQL Server, you will have to access the data
first before it is cached into memory. If you are a smaller organization it
shouldn't matter what repository
you are using. However, larger organizations may be more interested in
SAPH for in-memory and analytics capabilities.

For generalized use, you will more interested in SQL Server simply for the availability of API and third-party tools. See here
<https://db-engines.com/en/system/Microsoft+SQL+Server%3BSAP+HANA>

25 July 18
Ranking
7th
Views
12,968
Comparisons
7,709
Reviews
1
Average Words per Review
329
Avg. Rating
10.0
1st
Views
30,516
Comparisons
16,936
Reviews
30
Average Words per Review
419
Avg. Rating
8.4
Top Comparisons
Compared 40% of the time.
Compared 9% of the time.
Compared 19% of the time.
Compared 16% of the time.
Compared 15% of the time.
Also Known As
SAP High-Performance Analytic Appliance, HANAMicrosoft SQL Server, MSSQL, MS SQL
Learn
SAP
Microsoft
Overview

The SAP HANA® platform helps you reimagine business by combining a robust database with services for creating innovative applications. It enables real-time business by converging trans-actions and analytics on one in-memory platform. Running on premise or in the cloud, SAP HANA untangles IT complexity, bringing huge savings in data management and empowering decision makers everywhere with new insight and predictive power.

SQL Server is the Microsoft-driven relational database management system. This system is used to store data as well as retrieve it when necessary; these functions can be supported by individual users or by multiple users within a larger network. The Microsoft SQL Server has warehousing options, quality and integration services, management tools that are simple to implement, as well as robust tools for development.

Looking at the more technical end of things, Microsoft SQL Server uses query languages such as T-SQL and ANSI SQL. Disaster recovery is one of the product's most prominent features, in addition to in-memory performance, scalability, and corporate business intelligence capabilities.

Offer
Learn more about SAP HANA
Learn more about SQL Server
Sample Customers
Unilever, NHS 24, adidas Group, CHIO Aachen, Hamburg Port Authority (HPA), Bangkok Airways Public Company LimitedMicrosoft SQL Server is used by businesses in every industry, including Great Western Bank, Aviva, the Volvo Car Corporation, BMW, Samsung, Principality Building Society, Wellmark Blue Cross and Blue Shield, and the Catholic District School Board of Eastern Ontario.
Top Industries
No Data Available
REVIEWERS
Software R&D Company9%
Retailer9%
Comms Service Provider9%
Logistics Company9%
VISITORS READING REVIEWS
Comms Service Provider40%
Financial Services Firm25%
Transportation Company13%
Insurance Company8%
Find out what your peers are saying about Microsoft, Oracle, Teradata and others in Relational Databases. Updated: July 2019.
354,290 professionals have used our research since 2012.
We monitor all Relational Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
Sign Up with Email