HBase vs Microsoft SQL Server

• Scalability. HBase can scale to trillions of records.
• Fast. HBase is extremely fast to scan values or retrieve individual records by key.
• HBase can be accessed by standard SQL via Apache Phoenix.
• Integrated. I can easily store and retrieve data from HBase using Apache Spark.
• It is easy to set up DR and backups.
• Ingest. It is easy to ingest data into HBase via shell, Java, Apache NiFi, Storm, Spark, Flink, Python and other means.

Read full review

• Good range of data types helps us store lots of diverse data
• Easy administration helps us control who has access and what they can do with the data
• Backup and restore processes are easy to manage and provide good security
• Data can be easily replicated from Server to Server for use in other countries

Read full review

• There are very few commands in HBase.
• Stored procedures functionality is not available so it should be implemented.
• HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies.

Read full review

• Enterprise is unbelievably expensive.
• Not tolerant of bad practices and poor query writing, really shows up when you do it badly!
• Deep insight into what is happening with query performance is not especially great (but as mentioned in the "Pros", software support from third parties does cover this).

Read full review

• As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data.
• Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here.
• The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle.

Read full review

• With just one server we can easily host databases for many applications, which makes it easier to maintain.
• The ROI on Microsoft SQL Server is very good as we have been able to set it and forget with out too much time invested in keeping it up and running.
• The Microsoft SQL Server down time has been minimal and 90% of the downtime is due to our user error.

Read full review