Qlik Compose Reviews

We use it for clients who require effective communication through data and analytics tailored to their needs. It allows us to handle client data seamlessly and deliver customized data analytics solutions based on their preferences.

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

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. When it comes to end users who may lack technical expertise, they are limited to toggling between existing developments. To empower end users to make critical changes without relying heavily on technical expertise, it would be beneficial to introduce more user-friendly features for development and modification. If it could incorporate correlation analysis capabilities into its platform, especially in a user-friendly manner, it would greatly enhance the tool's overall utility and make it an even more outstanding solution. There is a room for improvement regarding stability.

I have been using it for almost a year now.

Stability has been a concern we've encountered, and I would rate it at approximately five out of ten.

We haven't encountered any challenges with it and we've been able to scale up effectively. I would rate it seven out of ten. In our organization, it is utilized by approximately two hundred individuals.

The technical support we received was excellent and I would rate them eight out of ten for their assistance.

Positive

We used Tableau, which offers better functionality and graphical representations than Qlik. While it may not reach the extensive features of Tableau, I lean towards Qlik Compose due to its cost-effectiveness compared to Tableau.

The initial setup is straightforward.

We brought in a consultant to handle the implementation and set it up for us.

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

Overall, I would rate it seven out of ten.

We primarily utilize Qlik Compose for development purposes, enabling us to supply data to business users. We employ transformation logic for the ETL processes, leveraging the staging layer data extracted from our source systems. Subsequently, we utilize this information, aligned with the business logic, to furnish Power BI reports to the users.

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.

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 have used Qlik Compose within the last 12 months.

Qlik Compose is a stable solution. If we have issues we contact the support.

We have 60 to 80 people using the solution.

The soltuinis scalable.

I have used the support. If we have issues we contact them and they provide us with a solution. They are good.

The initial setup of Qlik Compose is simple and took approximately one week.

The price of the solution is expensive.

I would recommend this solution to others. It is easy to use.

This tool provides a convenient solution for designing our warehouse swiftly. We can effortlessly incorporate any necessary changes or updates, minimizing both time and cost. Additionally, using this tool significantly reduces data versioning and enhances the efficiency of our BA projects.

I rate Qlik Compose an eight out of ten.

With Qlik Compose, it depends on what the customer wants to implement because it doesn't perform complex SQL statements without writing code. So in many cases, it's necessary to write the SQL directly to the database. I can say that it's not as simple as stated in the documentation because, in many cases, you have to write SQL code in order to perform some transformations. I say this because Qlik Compose is well known as a that can transform data in order to put them in a data warehouse. So in many cases, it's necessary to pre-transform the source data and then process them in Qlik Compose because the solution is used as a data warehouse automation tool. It is not a tool that performs some SQL modifications. For example, creating a transformation involving more than one table is extremely difficult. In the solution, the recent data quality functionality is a sort of controller of data. So, for example, if you wanted to perform a historical process to take all the modifications in some fields, it does it well.

The fact that in Qlik Compose, you can create the data marks without writing code, and you can connect to several databases as a target only by selecting the data targets and the credentials are some of its features.

Since it lacks in certain areas pertaining to scalability, there is a scope for improving the solution's scalability.

Qlik Compose should consider the fact that there are complex SQL statements without writing codes, documentation is not simple, SQL code is needed in order to make a transformation, and data quality functionality in the solution, and these issues need to be considered for improvement.

I have worked with Qlik Compose for two projects, and based on my experience, I used it to meet the requirements of my customer. So, it was a three-month project. My company has a partnership with Qlik Compose. Also, I am using the solution's latest version.

Stability-wise, I rate the solution a seven out of ten. 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.

Generally, my customers are enterprise-sized businesses. Scalability-wise, I rate the solution an eight out of ten.

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

Positive

It's very easy to install. Qlik Compose is not deployed on the cloud since it requires a client-server installation. The time for deployment depends on the needs of the customer. For one customer, we deployed it in three months. And for another customer, it took six months because the customer's needs were more. An architect and, in general, one or two people who are involved in the deployment process.

Regarding the maintenance of the product, during a project, the customer takes care of the maintenance part.

The pricing depends on the discounts that Qlik Compose. On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six.

I recommend other customers use Qlik Compose. I know that now Qlik Compose is improving a lot of functions and the overall product while implementing a lot of functionalities in the solution. So I think now Qlik Compose is on the correct path for the new implementation of new functionalities. Therefore, I think that no other functionality should be implemented at the moment.

Overall, I rate the solution an eight out of ten.

We used Qlik Compose for our data warehousing project. We were able to build the data nodes and schedule them effectively. Once the data was ready, we utilized it for our BI tools, including Power BI.

In our current project, one of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions. We achieved this using the Get Replicate tool, which allowed us to consolidate the data into a single data warehousing console source. From there, we were able to match and reconcile the data easily.

And we were able to use both full load as well as incremental loads as it was scheduled. We didn't have to manage many things from the implemented versus the full loads because Qlik was already providing the functionality to us.

So we faced some challenges in understanding the tool and raised a couple of tickets to better understand the tool. And the improvements, I would say, would be proper documentation. And there were certain keys or maybe columns that we could not understand, which were auto-generated.

So for that kind of documentation, if that was provided to us, we would have leveraged it more, or maybe some customization around that would be the approach going forward. We would leverage that and then use it accordingly.

I used it about seven months ago. Last I used it was in September 2022. 

It was a stable product, but they released new features and updates. The product release could be streamlined instead of sending patches for previous versions. We had to lag on the updates every time because we needed to check compatibility since it's a production environment. Releasing new versions in production was a little bit challenging for us.

It is a scalable solution. We had a lot of source systems, around eight to nine, and we brought all those systems' data to Qlik Compose without facing any issues in terms of scalability.

There were six people using Qlik Compose in our company at that time, including four to five other developers and one board lead.

We got proper responses from the customer service and support team. The support team was pretty good. We were expecting a certain response time, and we received distributed responses that did not get delayed anywhere.

Positive

The initial setup was easy for the data warehousing concept. But for a person who is new to ETL and warehousing concepts, it may take some time. If someone is familiar with these concepts, they could understand and learn the tool quickly. However, compared to other tools, the UI is complex. It would be helpful to have a better UI and documentation for new users. As of now, there is a challenge in learning the Compose tool for new users altogether. 

Qlik Compose was deployed on-premises. But the servers, like the SQL servers were maintained on the cloud—the managed instances.

We were a consulting firm implementing Qlik Compose for one of our clients. The client team and their manager chose Qlik Compose, so we didn't have much role in choosing the tool.

As the first tool, I would not recommend it. There was no proper UI, and the documentation was lacking in some areas. Training could have helped. There were two parts to it, data flows before data mask, and data was getting replicated from the sources. Some lineage graphs were there, but a better UI for ETL processes would have made it more feasible. But initially, I would say it's better to explore tools like Matillion, which can be used specifically over the cloud and are better compatible with other technology stacks apart from Qlik Compose.

Overall, I would rate the solution an eight out of ten. There is some scope for improvement around the documentation, and there aren't many users using it right now compared to tools like Matillion. We had to troubleshoot on UI and had difficulty finding resources online. A better UI would definitely help.

It is primarily a data integration tool for us. When it comes to the Qlik data integration aspect, it was extremely complete and one of the best platforms I've seen.

I work with a company that is focused on data integration, and Qlik was the preferred tool.

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. They could create a data hub for clients with all the protection and features needed. 

Some of the other features include data warehouse automation, CDC's training, managed Data Lake Creation, and Guardant Data catalogs, which were very useful in analytics applications. It's not the most complete tool for data integration, but it is still impressive.

Currently, Qlik's ETL and data transformation could be better. Also, the implementation can be improved because it is complicated. At first, it's really difficult for partners and clients to understand the platform and to work with it. The integration is very siloed within the IT department and IT architecture teams, which causes friction when trying to distribute it to businesses.

Additionally, they don't have the most user-friendly platform for visualizing data. Qlik was initially a data visualization tool, but it became a full data pipeline company after acquiring many companies. However, even after three or four years, they still have some challenges with data integration implementation within the clients.

Moreover, their support team could also be better. The support is also not very good.

Qlik Compose is a legacy product opportunity that is more focused on the data integration side. Qlik has a whole pipeline that goes from data integration to data literacy. So, I have some experience with Qlik Compose.

Qlik should have more people working for support and be faster, especially for large clients. The SLA is 24 hours for large clients, which is ridiculous whenever you have companies that can solely chew. Oftentimes, they do not respond within 24 hours, so there is an issue with internal communication when we have an issue with support. There is a lot of room for improvement in Qlik's support team.

Neutral

Overall, I would rate Qlik compose an eight out of ten. It is a good platform. 

We use Qlik Compose as a low to no-code data warehouse and data lake generation tool. I use it to build data warehouses and data lakes.

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.

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.

I have been involved with Qlik Compose for about six years.

Qlik Compose is a stable solution.

On a scale from one to ten, I would give stability an eight.

Qlik Compose is a scalaible solution. If you are in the cloud, scaling is straightforward. If you are on-premises, you are scaling by adding either RAM or space, which can be a bit more challenging. If you look at their documentation, it has a relatively straightforward grid-type thing.

On a scale from one to ten, I would give scalability a seven.

Their first level of support could do with some improvement. If I log a call or submit a problem, I tend to find that I have to repeat myself because the person who first gets it is the first level of support. They do the same kind of thing, and they have a script. They ask questions like "have you rebooted? Have you checked this, or have you done that?"

On a scale from one to ten, I would give technical support an eight.

Positive

The initial setup is straightforward. It takes about 20 minutes to deploy this solution.

On a scale from one to ten, I would give the initial setup a nine.

On a scale from one to ten, I would give Qlik Compose an eight.

I have used the solution for warehouse modeling and auto-mapping features.

The solution's most valuable feature is auto-mapping. It provides an in-built layout for the warehouse. So we don't have to do the modeling from scratch. It gives us an overview of the basic model, which we can build from there.

The solution's setup process could be more straightforward. They should add proper documentation to understand the procedure for implementation.

I have used the solution for one year and eight months.

The solution is relatively stable. I rate its stability as an eight or nine.

The solution is scalable. I rate its scalability an eight or nine.

The solution's initial setup process is complicated compared to Replicate. It is time-consuming and requires improvement.

I rate the solution as a seven. The intermediate-level executives can operate it easily compared to the beginners.

We use the solution for data modeling and segregation.

The solution's most valuable features are data modeling and segregation. They make the processes easier.

They should add more functionality to NoSQL databases. There could be more customization options as well. In addition, they should improve the solution's integration with Linux systems.

We have been using the solution for more than four years.

It's a stable solution. Although, there were some stability-related errors. They were resolved in the short-term patch release. 

We have more than 3000 solution users as our customers.

The solution's initial setup process is complicated.

Compared with other products available in the market, the solution is easier to use and has more functionality. I recommend it to others and rate it as a ten.

I'm not a primary user. I'm a developer and have implemented it. We don't use it alone. We use it with Qlik Replicate, which does real-time replication of data. Once the data lakes are created, we can use Qlik compose for creating data warehouses, for example. 

The real-time replication is useful. 

Overall, it works quite well. 

Of all other products, Qlik is very easy to use. Tasks can be done via drag and drop.

It is very stable.

Technical support is helpful.

It can scale. 

We face some issues with data replication, however, Qlik helps us resolve issues.

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

They need to add in more ETL features. 

I've implemented the solution multiple times. I've used the solution for about a year. Last year, in July, we did an implementation, and we completed it in two to three months.

For now, it is stable, yet not 100%. Sometimes, errors occur. We do get the support that helps resolve issues. 

The scalability is good. It is not an ETL tool like others on the market. 

Technical support is helpful and responsive. 

Positive

We've used Qlik Replicate as well as Talend.

The initial setup is very easy. The tricky part is making connections between data sources and targets, as each has separate procedures to make data connections. For example, with SAP, authorization is a major part of the process. 

We can implement the solution for our customers. 

If companies are able to achieve real-time reporting, the price of the solution is worth it, and the company would get an ROI. 

The pricing varies according to the data, including how much you have. It depends on what the company is doing and how much data they are working with. 

We are implementation experts and partners of Qlik. 

I'd recommend the solution depending on the use cases. If a company needs real-time reporting, I'd recommend the solution to them. 

I would rate the solution seven out of ten. They need to add ETL features, although the automation they have is very good so far. In the future we'd like to see more customization in the future. 

Our company uses Qlik Compose for simple transformations. We use it as a basic ETL solution. 

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

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.

Qlik also needs the ability to improve more complex combined SQL tables and perform more complicated transformations. I'd like to see better connectivity to some with custom coding languages like Python or Java.

We've been using Qlik Compose for about a year and a half.

Qlik Compose is stable. We haven't had issues except when dealing with high volume. Otherwise, it's okay. 

I don't think Qlik can be used in a high-volume scenario. It didn't work for us.

Support is okay. We don't get the required solutions on time, so I would just say support is average. Yeah.

Setting up Qlik Compose is straightforward. You only need one person to deploy and maintain the solution. 

It was an in-house deployment.

I would Qlik Compose six out of 10. You should understand the product well before using it because it has a learning curve. There are many options, so if you choose the wrong one, you may get stuck with it. If you're trying to do something with high data volumes, this may not be the right choice at the moment.