Qlik Compose Reviews

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.

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.

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.

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.

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

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.

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.