Qlik Replicate Reviews

Most of the use cases involve changing the data capture and dealing with data replications. The main use case is data replication.

All real-time data migrations are happening through Qlik.

Its capability to replicate the data without impacting the source databases performance-wise is the most useful aspect. In terms of the databases, what they do is they don't actually connect to the database and capture the data, and so they go with the logs. They, handle logs and capture the changes from there, and push those changes in real-time. The delay is in milliseconds. Within milliseconds' time, I can move the data to other databases. It's almost real-time for handling my real-time analytics. 

The solution is stable.

Support has been great.

They can do a better job in the performance. They don't do much compression on the data migration. That's the one thing they need to fix. We'd like better connectivity.

Initial migrations are taking up too much time. They can improve on replicating to multiple targets.

We've been using the solution for almost two years now.

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash.

The product is not really scalable. However, we can scale it with a little effort.

Mostly data engineers are using the product at this time. 

Technical support is good. We get all the support we need. They are open for making changes as well for any issues.

I did the POC only. The implementation and everything was done by the other team.

My understanding is that it's not too hard, however, it's not exactly easy either. Sometimes we need assistance from Qlik.

It took more than a week to deploy as we had a lot of other things already. There were a lot dependencies, including databases. There are a lot of other dependent configurations as well. We had to change the data capture, et cetera.

We have three or four people that can handle deployment and maintenance. They are engineers. 

We occasionally may need assistance from Qlik during implementation. We mostly handled the initial setup in-house, however.

I'm not sure of the exact cost of the solution. It depends on how you negotiate. Most products in this area have a similar cost. They are generally flexible. 

We are customers. 

It's implemented on both the public cloud and on-prem.

I'd rate the solution seven out of ten.

I'd advise potential users to review this product and see if it fits their needs. If it does, they should try it out. 

Our main use case is replicating a source database to another database in order to have the information ready for our analytic users close to real-time and for use in different business intelligence software. I'm a solutions architect. 

Replicate has improved our performance in the database source. It also has the ability to have many analytic users doing different SQLs against the target data source. We've been able to improve the performance in the source without affecting the operational users.  

The most important feature is around replicating and updating records. We previously had to employ a programmer to replicate the difference between target and source and we no longer need to do that. 

An issue we have is that it's not possible to replicate the QVC files in data analytics. It would be helpful if they could solve that. When it comes to metadata, the business name of the fields could be improved to have a catalog very close to the user to link the technical names to the business name.

I've been using this solution for two years. 

We haven't had any issues with stability. 

We're happy that we have access to Spanish-speaking support and they provide a good service.

The initial setup is very simple. It's a matter of choosing your source database and then your target database. The configuration is easy. 

We've seen an ROI in terms of time and money, particularly where workers have been able to turn to other tasks because they have more time. 

Licensing costs are reasonable and depend on your needs. 

We are achieving our goals with this solution. It's important to compare the products on the market to find which best suits your use case. I rate this solution eight out of 10. 

We use this solution for data warehouse replication. It is used by three network developers in our company. 

It's very user-friendly when it comes to settings and configuration. It also offers very detailed logging about warnings and errors.

We would like to see more details in messages about errors with the system.

I have been using this solution for one year. 

This is a stable solution. 

We use a local company for support and do not rely on Qlik support. 

Before using Qlik Replicate we used to use QlikView and Qlik Sense for data visualization. Our vendors recommended to use Qlik Replicate instead.

The initial setup is very straightforward. There is a recommendation on the Qlik website about database configuration and there is very good step by step manual for getting set up.

Qlik Replicate offers an annual subscription, but after five years a solution like GoldenGate offers a lower price. Overall, Qlik is an expensive solution. You need to pay for all additional features that you would like to use. 

I would rate this solution a nine out of ten. 

We use EC2 for the cloud service for Qlik Replicate. We generally use Qlik Replicate from SQL server source to SQL server source destination, or to the AWS RDS instance. Either a single server on-premise or AWS RDS Postgre Aurora.

Qlik Replicate has improved our organization because it has allowed each team the ability to do their own data replication into our single-source data, such as data lake or our AWS. All the data can be moved to a single location.

The most useful functions of Qlik Replicate are data manipulation and transformations.

When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating.

When we do receive errors when the solution suddenly fails it will give a message of  "Error." You have to go and figure out which setting you have to tweak to get the actual error. This could be improved by being more descriptive or more intuitive. They have eight different options of things the error would say, such as enhance logging, but you don't really know what that means. The wording doesn't tell you if it fails. It makes it difficult when trying to find the actual problem.

In a feature release, they could improve the solution by making it easier to use two different destinations. If we want to do have on-premise and in the cloud, it seemed difficult when I was attempting the process. It would be useful to just have one source and then two different destinations, using the same transformations and other configurations.

I have been using Qlik Replicate for approximately six months ago.

The scalability is very good because we are using Amazon AWS.

We have approximately 10 people using the solution in my organization and most of them are developers, such as software engineers. The solution is moderately used in our organization.

The technical support could improve. It is difficult to connect with them on the phone. There can be a lot of back and forth communication.

We previously used SSIS and an in-house built product.

We ended up choosing Qlik Replicate because we were doing a lot of transforms, and decided to list the data in one place. Qlik Replicate was a good product to get data over without turning on a CDC. We wanted a tool that was easy to use and we decided Qlik Replicate was right for us.

The initial setup involved setting up the source and the privileges needed on every source. DBAs don't like that too much, but they have to give each team access privileges but that's the only way to use Qlik Replicate. Additionally but then the troubleshooting and stuff, it took about a month just getting all the stuff right, all the details. The initial additional troubleshooting and other aspects of the implementation took about a month to have all set up correctly.

We did the implementation in-house. The solution has not needed a lot of maintenance, we do not have an assigned individual for maintenance.

We are evaluating other solutions at this time, such as DM, which uses Qlik Replicate in the background.

Overall the solution is straightforward to use. It does a good job at what it needs to, but it's not as robust in the transformations, for example, the lookups.

I rate Qlik Replicate a seven out of ten.

Our primary use case is to transform and modernize our analytics environment and modernize the data pipelines.

It enables us to transform data at the latest stage rather than in ETL loads, so it's more ELT which is one of the advantages. It is also in near real-time, which brings significant advantage for our embedded analytics approach.

We have technical people who work with it. I do not have a lot of feedback to provide at this stage. We want to implement a data lake but that's at the second stage to be integrated with the other tools that we use, which are Qlik. Since we use Qlik, we intend to leverage Attunity's capabilities because Attunity is now part of the portfolio.

I have been using Qlik Replicate for around two months. 

We've had a team of consultants helping us directly. So we do not use support now. We are in the phase where we're really working with the consultants from Qlik now.

It was easy to set up. We had specialists who helped us with the setup. We have around three users. 

It's being used daily. 

It's extremely promising. It implements new real-time capabilities for data ingestion. It works in hybrid mode that is a hybrid cloud. This is very good and it looks like it has very good performance. We're quite happy.

I would rate it a nine out of ten.

In the next release, I would like to see closer integration with data catalyst.

I am a consultant who is using Qlik Replicate for one of our customers. It is primarily used for the historical load, as well as the incremental load.

Our current project involves a client that has their legacy data in SAP HANA. They want to transfer all of the data from SAP into Snowflake. It involves terabytes of data and Qlik is being extensively used.

From a technical perspective, this is an excellent product.

Qlik can be made more user-friendly.

Support-wise, this solution is in need of improvement.

We have been working with Qlik Replicate for almost one year.

This product is very stable.

The scalability is very good. My customer has about ten people who are using this solution.

When we reach out to technical support, they should be good enough to support us.

When we reached out to them to assist with doing the PoC for our customer, they declined my request. Our customers were trying to access their data and when we asked certain questions from the Qlik folks, they were heavily focused on the licensing issue and wasted time with that while we could have been solving the problem.

By comparison, when I speak with HVR technical support, they never ask anything like this. Rather, they will directly help us. They receive the problem and straightaway they will try to help us. This enables us to better speak with our customers.

We are a partner, and when we want to reach out to the Qlik experts, we would like to receive answers.

Overall, I would rate their support a four out of five.

I have used HVR and I feel that it has more features than Qlik. It is also more customer-friendly.

Feature-wise, I cannot think of any improvement that is needed. We are very happy with Qlik, no doubt about it. The only problem is with support. When we ask for technical assistance they should be in a position to support us.

I would rate this solution a ten out of ten.

Qlik Replicate is a product used to replicate data. 

A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product. 

This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved. 

Qlik bought Attunity, and I was working with Attunity Replicate for more than 10 years. 

Qlik Replicate is stable. 

This solution is scalable. 

Qlik Replicate is not expensive, compared to GoldenGate. 

The competitors of Qlik Replicate are Oracle GoldenGate and Sybase Replication. 

I rate Qlik Replicate an eight out of ten. 

To someone looking into Qlik Replicate, I would say that it's easy to use and Qlik Replicate is only one part. You should know the data to replicate it. It's a technical solution. If you are an integration consultant and you are using a replication tool, you should also know ETL tools to complete the picture. If you want to use Qlik Replicate, you should also focus on the ETL side.