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

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

"I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years."

"One of the most valuable features of this tool is its automation capabilities, allowing us to design the warehouse in an automated manner. Additionally, we can generate Data Lifecycle Policies (DLP) reports and efficiently implement updates and best practices based on proven design patterns."

"It can scale."

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

"It's a stable solution."

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

"There is room for improvement in the pricing."

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

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

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

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

"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."

"There could be more customization options."

"There should be proper documentation available for the implementation process."

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

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

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