IBM Db2 Big SQL vs. Starburst Enterprise

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

If you run a SQL query, Starburst Presto can help you track efficiently the status of SQL query. It can also track how many resources have been allocated for execution and what is the optimal way to run the query without hindrance. It also provides good information on worker nodes and how parallel threads are running together.

Incentivized

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

Incentivized

• Query tracking.
• Resource allocation.
• Parallelizing query execution.

Incentivized

• Cloud readiness.
• Ease of implementation.

Incentivized

• Pricing
• Platform can be made more intuitive.
• Sometimes the platform hangs while aborting the query.

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

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

Most of our systems were compatible with Starburst Presto. The dashboard which they provide was fairly intuitive and easy to use. The learning curve wasn't that much. Also, the parallel processing part was an additional feature that we didn't find in many competitive products. The pricing was a little higher but it was worth the trade-off.

Incentivized

• better data visibility
• solid reliability for mission critical data

Incentivized

• Neutral impact.
• ROI on saving time for query execution.
• Parallel processing saves time too.

Incentivized