Qlik Compose vs Upsolver comparison

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

"It can scale."

"It is a scalable solution."

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

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

"It's a stable solution."

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

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

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

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

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

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

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

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

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

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

"There is room for improvement in query tuning."

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

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

"The price of the solution is expensive."

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