Qlik Replicate enables organizations to accelerate data real-time replication, ingestion and streaming via change data capture, across a wide range of heterogeneous databases, data warehouses and data lake platforms.
N/A
SSIS
Score 8.4 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
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. …
Qlik Replicate / Attunity was able to be put on our server behind our firewall where with Fivetran would have required. Fivetran would also have required a different SQL server CDC setup. HVR was just as powerful if not more but was more costly and the user interface was not …
Simple to do one-to-one copy and very reliable, as other tools a little complex in setting up the pipelines and scheduling parts. Very simple to connect to the SFTP locations and easy to download them as well.
We selected Qlik Replicate because it was the easiest to use with the least network overhead. The team was able to master the application in under an hour--significantly less than IBM or Informatica.
Qlik Replicate works very well with relational data platforms, both on premise and in the cloud, for example Oracle, SQL Server, PostgreSQL, MySQL and others, it also works very well with DB2. If the data source is MongoDB, it is more complicated and currently there is no possibility of sending data to MongoDB.
Ideal for daily standard ETL use cases whether the data is sourced from / transferred to the native connectors (like SQL Server) or FTP. Best if the company uses MS suite of tools. There are better options in the market for chaining tasks where you want a custom flow of executions depending on the outcome of each process or if you want advanced functionality like API connections, etc.
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.
The base Replicate web GUI is lacking. If you have dozens or more tasks, it's hard to get a sense of how they're performing. Enterprise Manager solves all of these problems but is a separate install.
The support portal is extremely difficult to navigate. It's hard to track down exactly what you're looking for.
It would be helpful to have better documentation and example queries for the tables in the Enterprise Manager analytics database.
Destination databases that don't support common DDL commands behave unpredictably. And the replication of schema changes isn't consistent.
SSIS has been a bit neglected by Microsoft and new features are slow in coming.
When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.
The availability of the replicated data in disparate environments has is now crucial. Replacing a product like Qlik Replicate would require significant time, investments, and work. In addition, Qlik Replicate is reasonably reliable with few failures.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
We now have greater business flexibility and scalability, and our big data integration projects have a quick rate of growth, which has been profitable for us. Independent of the sources involved, maintaining data consistency between sources is easy. One of my favorite features is the way it lets owners of the source system start and stop processes from updating their system windows.
SQL Server Integration Services is a relatively nice tool but is simply not the ETL for a global, large-scale organization. With developing requirements such as NoSQL data, cloud-based tools, and extraordinarily large databases, SSIS is no longer our tool of choice.
Raw performance is great. At times, depending on the machine you are using for development, the IDE can have issues. Deploying projects is very easy and the tool set they give you to monitor jobs out of the box is decent. If you do very much with it you will have to write into your projects performance tracking though.
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.
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
Follow the directions from the Qlik documentation. They are pretty straight forward and easy enough to follow. If you follow these, then you are not likely to have issues on implementation.
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
Great tool for data replication solution for Oracle/SQLServers/etc. Real easy to get it set up and start realizing business value. Getting the PoC accomplished in a short window. Product costing and easy to start small and scale as needed. It helped cover most of our ask compared to other solutions.
I had nothing to do with the choice or install. I assume it was made because it's easy to integrate with our SQL Server environment and free. I'm not sure of any other enterprise level solution that would solve this problem, but I would likely have approached it with traditional scripting. Comparably free, but my own familiarity with trad scripts would be my final deciding factor. Perhaps with some further training on SSIS I would have a different answer.
Prior to using Qlik Replicate, we used an ETL solution to copy data from the Oracle ERP system to the Microsoft SQL Server BI system at a 15-minute interval. It was very tedious to maintain. Qlik Replicate is much easier to use and we replicate data near real-time now.
