Utilize Qlik Replicate to Streamline Your Data Into Your Data Warehouse and Build Your BI Platform Faster!
June 10, 2021

Utilize Qlik Replicate to Streamline Your Data Into Your Data Warehouse and Build Your BI Platform Faster!

Darin Coulter | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Qlik Replicate

We use Qlik Replicate in one specific vertical within our larger organization. We are using it to copy transactional tables from our CRM database into a data warehouse so that we can build a business intelligence suite on top of that data in an OLAP database. Qlik Replicate allows us to easily copy that data without our having to build our own custom, real-time ETL processes.
  • Replicate is extremely stable and does not generate a lot of alerts/failures/issues that take up time to troubleshoot.
  • It is very easy to add new source tables to a Replicate task so that we're always in sync with new data available from the CRM.
  • It's nice that Qlik Replicate also allows you to create a job to stop and then restart your tasks during maintenance windows that occur on both the source and target systems.
  • I wish there was a way to give the user the option to decide if changing a particular task setting actually requires a reload of the target table. Too many changes or modifications within the task settings require you to reload a table and if the target database and source database do not have the same data retention policies then you risk losing data and you have to account for that when changing task settings.
  • From time to time a particular task begins to build up latency where it becomes 2,3 or 4 hours behind the source system. It's never really clear why that is occurring and it may be impossible to know exactly but I wish there was a way to know that it was due to activity happening at the source or the target.
  • It has improved our time to market to be able to get at source data faster and in an OLAP vs OLTP database.
  • It frees up database analysts time to be focused on the operational intelligence rather than the building/maintaining of complex ETL processes.
Qlik Replicate's power is in its simple 1:1 copying of database tables and architecture and maintaining a near real-time copy of that database. Talend and SSIS are different tools and more for custom ETL's that require various steps to connect to SFTP or download files. They're not really similar in how I've used them but I wouldn't want to re-create the easy replication that Qlik Replicate does in either platform.
Everything that I use (Vertica and DB2) has ODBC connections so its very easy to set up your connections and start replicating data.

Do you think Qlik Replicate delivers good value for the price?

Yes

Are you happy with Qlik Replicate's feature set?

Yes

Did Qlik Replicate live up to sales and marketing promises?

Yes

Did implementation of Qlik Replicate go as expected?

Yes

Would you buy Qlik Replicate again?

Yes

We don't really use a lot of the more advanced features of Qlik Replicate (like transformations) but I feel like Qlik Replicate is very good at the simple 1:1 replication of source to target. It provides you a way to view change tables to see how/when attributes within source tables changed. It's great for business groups that may not know as much about building an ETL but it would get the data they need into a non-production environment to query/investigate/report on certain aspects of their business without the necessity of a giant IT budget.

Using Qlik Replicate

1 - Data Analysts
1 - These are data analysts with SQL knowledge and an understanding database architecture but also people that understand how to visualize data in order to tell an effective story.
  • Copy data from transactional system to data warehouse
  • Allow business users to be the power users of the Replicate tool
  • Get data into a data warehouse without IT intervention
  • We haven't really been that innovative with Replicate
  • Taking advantage of the transformation tools
We like the product and it serves us well with its stability and ease of use.

Evaluating Qlik Replicate and Competitors

  • Price
  • Product Features
  • Product Usability
Find more products that are similar to Qlik Replicate and not traditional ETL interfaces.

Qlik Replicate Implementation

A lot of the process was done by an Attunity or Qlik engineer and there wasn't a lot of knowledge transfer to feel comfortable about maintaining the software without their help.
  • Implemented in-house
  • TIBCO professional services
Change management was minimal
  • Making sure that we had target tables built properly (with primary keys) so that bulk load/update processes were being processed one by one.

Qlik Replicate Support

ProsCons
Kept well informed
Slow Resolution
Poor followup
Less knowledgeable
Problems left unsolved
Escalation required
Difficult to get immediate help
Support doesn't seem to care
Slow Initial Response
I believe we have premium support but I am unsure (which speaks to some of the issues since Qlik bought out Attunity).
I do not have such an example with Qlik. I used to have great interactions when it was Attunity Replicate and Dan Cleary from the support team always knew how to help resolve our issues with the DB2, AS/400 source.
The issue I've had is that Qlik does an awful job of keeping their customers informed when new versions of the software are available. We found that we were using a version that was no longer supported and could never get help. When it came time to get us upgraded so that we were on a current version, no one knew how to help get us to where we needed to be. We had to purchased professional services time and even then I was basically on my own to get everything built out and set up. Qlik needs to be more proactive with communicating about new releases and how to get your version upgraded in the most secure, safe way possible.

Using Qlik Replicate

ProsCons
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Consistent
Quick to learn
Convenient
Feel confident using
Familiar
None
  • Setting up data connections
  • Creating new Tasks
  • Setting up Tasks with tables, filters and transformations
  • Upgrading software versions
  • Working with Qlik Support

Upgrading Qlik Replicate

Yes - We had a more involved upgrade process because we were still using an old, unsupported version of Replicate because we didn't know we needed to upgrade previously. This caused the upgrade process to be a lot more involved and much more difficult.
  • Getting on a supported version
  • Getting rid of old software like the Attunity Server that was harder to use
  • Being able to set up ODBC connections rather than having an agent installed on the source