Apache HBase vs. Microsoft SQL Server

Hbase is well suited for large organizations with millions of operations performing on tables, real-time lookup of records in a table, range queries, random reads and writes and online analytics operations. Hbase cannot be replaced for traditional databases as it cannot support all the features, CPU and memory intensive. Observed increased latency when using with MapReduce job joins.

Incentivized

Microsoft SQL Server is a great RDBMS and meets all of our requirements. If you need a stable DB platform to support your line of a business application you'll be well served. Licensing costs are far cheaper, more portable and a lot more user friendly than Oracle. Product support and security patches from Microsoft are strong.

Incentivized

• 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.

Incentivized

• Easy to configure and use with Visual Studio and Dot Net
• Easy integration with MSBI to perform data analysis
• Data Security
• Easy to understand and use
• Very easy to export database and tables in the form of SQL query or a script

Incentivized

• 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.

Incentivized

• The import/export process can be tricky to follow with lots of steps and could be better for importing flat files
• Obtaining help from Microsoft is cumbersome and often other internet sources are better and quicker
• The documentation is not great and again it's generally better to obtain help elsewhere if needed

Incentivized

There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.

Incentivized

We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.

Incentivized

SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.

Incentivized

Its does not have outages.

Incentivized

SSAS data cubes may some time slow down your Excel reports.

Incentivized

We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.

Incentivized

It was good

Incentivized

very hands on and detailed training

Incentivized

Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.

Incentivized

Cassandra os great for writes. But with large datasets, depending, not as great as HBASE. Cassandra does support parquet now. HBase still performance issues. Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.

Incentivized

[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.

Incentivized

SQL server does handle growing demands of a mid sized company.

Incentivized

• 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.

Incentivized

• Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
• Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
• Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.

Incentivized