Apache Druid vs. SAP SQL Anywhere

It is extremely well suited to rapid ingest of data from large data sources, due to the fact that you can restrict what is ingested by column/field, so that you only pull in the data you actually want or need.

As stated earlier, the open source version could use better cluster management tools, and troubleshooting tools for failing jobs/tasks.

SAP SQL Anywhere is better than not using a database, let's be clear there! However, I wouldn't pick it as my first or even second or third choice. I'd recommend looking at other options. Largely, it appears less powerful both in terms of its robustness and general performance and in its implementation of SQL. The standard Sybase utilities provided are lacking in basic features, and the interactive SQL utility is quite horrendous. However, the great thing is it is an ODBC-compliant SQL-compliant relational database.

Incentivized

• Rapid ingest
• Limiting ingest to only the relevant fields/columns
• Easy ingest spec creation

• Good performance with relatively large data sets - its cost-based query optimizer is particularly robust
• ANSI SQL compliant
• Supports T-SQL
• Scales well between the desktop (single user) and client/server installations supporting 50-1000 users

• Security configuration is problematic
• Cluster management could have more features
• Troubleshooting incomplete tasks/jobs is a chore

• I think it should be more user friendly for non-technical users.
• More functional functionalities should be added to the object explore when working with a table to transform data/manipulate data.

Incentivized

Ease of use, relationship to existing software's used in house and familiarity with the product

Incentivized

I worked with Oracle for years during my career. I wouldn't select SQL Anywhere to implement a global ATM system with tens of thousands of concurrent connections, but SQL Anywhere is much easier to use and deploy and works very well in workgroup settings. Query performance often exceeds some Oracle versions without having to rely on database tuning.

• Integration with S3 storage has saved about 35% on our storage, over HDFS
• The rapid ingest has saved user's time in the query aspects of their applications.
• The ability to ingest from a variety of data sources has made overall user application queries much simpler

• Skilled/experienced resources are less prominent than Microsoft SQL Server or even Oracle, or MySQL, so finding solutions and assistance, if needed, takes more time than it would with other platforms
• You will need to find a good SQL query tool by yourself because the Sybase Central / Interactive SQL utilities are lacking in many basic features, and just generally have a bad user interface

Incentivized