Qlik Compose vs TetraScience comparison

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

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

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

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

"It's a stable solution."

"It is a scalable solution."

"The ingestion engines were pretty good."

"The crawler agents they provide, as well as TetraScience exclusive parsers, allow for specific instruments that we use in our labs with proprietary formats to extract data and put it into more standard formats for various purposes."

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

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

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

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

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

"While functional during ingestion workflows, the automation toolkit required manual processes."

"The application has a difficult-to-use parsing capability, which requires a lot of reengineering when the use case isn't specifically met."

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