IBM Db2 Big SQL vs. Red Hat JBoss Data Virtualization

My recommendation obviously would depend on the application. But I think given the right requirements, IBM DB2 Big SQL is definitely a contender for a database platform. Especially when disparate data and multiple data stores are involved. I like the fact I can use the product to federate my data and make it look like it's all in one place. The engine is high performance and if you desire to use Hadoop, this could be your platform.

Incentivized

Red Hat JBoss Enterprise Data Services is a top choice for JEE applications. Even though lots of documentation is available, it's difficult in terms of usability. If the development is more based on Java applications it is a good choice. It provides better installation and integrations.

Incentivized

• data storage
• data manipulation
• data definitions
• data reliability

Incentivized

• Data source compatibility: since it is Java, it can connect to anything with a JDBC driver.
• Flexibility: you can configure it however you want, we have it configured to use LDAPS for authentication and have all interfaces encrypted, and setting that up was pretty straight forward.

Incentivized

• Cloud readiness.
• Ease of implementation.

Incentivized

• Pricing
• User Interface

Incentivized

IBM DB2 is a solid service but hasn't seen much innovation over the past decade. It gets the job done and supports our IT operations across digital so it is fair.

Incentivized

IBM did a good job of supporting us during our evaluation and proof of concept. They were able to provide all necessary guidance, answer questions, help us architect it, etc. We were pleased with the support provided by the vendor. I will caveat and say this support was all before the sale, however, we have a ton of IBM products and they provide the same high level of support for all of them. I didn't see this being any different. I give IBM support two thumbs up!

Incentivized

Support availability and resolution response time make it a better choice.

Incentivized

MS SQL Server was ruled out given we didn't feel we could collapse environments. We thought of MS-SQL as more of a one for one replacement for Sybase ASE, i.e., server for server. SAP HANA was evaluated and given a big thumbs up but was rejected because the SQL would have to be rewritten at the time (now they have an accelerator so you don't have to). Also, there was a very low adoption rate within the enterprise. IBM DB2 Big SQL was not selected even though technically it achieved high scores, because we could not find readily available talent and low adoption rate within the enterprise (basically no adoption at the time). We ended up selecting Exadata because of the high adoption rate within the enterprise even though technically HANA and Big SQL were superior in our evaluations.

Incentivized

Market value and support extended by Redhat is the winner against Veritas. It has cool features and functionality but still, if your organization is Redhat shop it's better to go for the Jboss option.

Incentivized

• better data visibility
• solid reliability for mission critical data

Incentivized

• It has allowed us to start moving applications independent from their underlying data sources, savings us time and limiting cutover effort.

Incentivized