Qlik Compose vs Upsolver comparison

"It's a stable solution."

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

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

"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 is a scalable solution."

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

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

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

"The most prominent feature of Upsolver is its function as an ETL tool, allowing data to be moved across platforms and different data technologies."

"It was easy to use and set up, with a nearly no-code interface that relied mostly on drag-and-drop functionality."

"Customer service is excellent, and I would rate it between eight point five to nine out of ten."

"There could be more customization options."

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

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

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

"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."

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

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

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

"On the stability side, I would rate it seven out of ten. Using multiple cloud providers and data engineering technologies creates complexity, and managing different plugins is not always easy, but they are working on it."

"Upsolver excels in ETL and data aggregation, while ThoughtSpot is strong in natural language processing for querying datasets. Combining these tools can be very effective: Upsolver handles aggregation and ETL, and ThoughtSpot allows for natural language queries. There’s potential for highlighting these integrations in the future."

"There is room for improvement in query tuning."

"The price of the solution is expensive."

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

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

"Upsolver is affordable at approximately $225 per terabyte per year."