Census vs Qlik Compose comparison

"Based on delivery metrics and team feedback, the benefit is that the time to activate new use cases was reduced from weeks to days, engineering effort dedicated to reverse ETL pipelines decreased by sixty to seventy percent, maintenance overhead for custom integration was almost completely eliminated, and marketing and growth teams accelerated experimentation cycles significantly."

"Through automation, we have been able to save between forty and sixty percent in time and cost, thanks to the automation platform and automation 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."

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

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

"It's a stable 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."

"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 areas for improvement are complex transformation logic because it must still be handled upstream in the warehouse, and cost predictability requires attention at high data volumes."

"One area that may need improvement is that sometimes a custom setup is very difficult to configure."

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

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

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

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

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

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

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

"The price of the solution is expensive."