Oracle Big Data SQL vs Qlik Compose comparison

"The user interface is really user-friendly and intuitive."

"This solution can maintain a large volume of data and is flexible to what data it can handle. The performance is very good."

"Qlik Compose is good enough. It is user-friendly and intuitive."

"I have found it to be a very good, stable, and strong product."

"It can scale."

"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."

"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."

"The technical support is very good. I rate the technical support a ten out of ten."

"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."

"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."

"There is room for improvement in the pricing."

"The solution could improve by adding more advanced features."

"There is some scope for improvement around the documentation, and a better UI would definitely help."

"I'd like to have access to more developer training materials."

"Qlik's ETL and data transformation could be better."

"I believe that visual data flow management and the transformation function should be improved."

"My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working."

"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."

"It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model."

"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."

"The price of the solution is expensive."

"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."