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 6.5 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
I found this as my lifesaver in terms of its efficacy and approachable to scale the streaming data from our ecommerce platform and analytics of data made much easier than compared to others. As it's partners with azure and other platforms which made our applications faster to …
We tried to use Oracle GoldenGate for our Oracle source replication needs but, had too many issues with a number of our tables due to churn or size. Qlik Replicate had no issues. And, we can tune our tasks to not impact the source systems we are pulling from.
Director -Enterprise Architect and Technology Strategist
Chose Qlik Replicate
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 …
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 …
Qlik Replicate was more manageable, very intuitive and easy to understand than the other products like Striim. The learning curve is less with Qlik Replicate and the connectors for various sources was easier to plug and play.
The biggest advantage of Replicate in comparison to Fivetran is that we can run the application on-prem. This allows us to configure it precisely how we desire, avoid opening additional ports in our firewall, and monitor its resource consumption directly. That level of …
We replaced IBM’s Change Data Delivery software (Change Data capture specifically for Netezza) because it had a bad user interface, it was difficult to set up, and it was very hard to troubleshoot errors. We selected Qlik Replicate (then called Attunity CDC) because it has a …
Attunity: Easy interface, relatively easy monitoring, zos support, budget friendly. we choose Attunity. At the same time we use AWS DMS for DB2, sqlserver -> aws services replications (cheaper). However because AWS DMS does not support db2 zos we use Attunity for db2 zos …
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.
You need to have expertise knowledge to design and develop data using visual studio. But you can design a data flow with minimum experience. In addition to that QLIK has a better performance. It enables you to replicate a large volume of data with minimum latency. The …
We helped attunity (prior owners if replicate) build out new features and worked through bugs with them. Their product was not great when we originally started but there were no other solutions in the market except for Golden Gate which had a hefty price tag associated with it.
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. …
We tried MIMIX, SQL SSIS and Veeam but our team found Qlik Replicate had an advantage over all these three in terms of speed, UI, and ease of maintenance.
Sr. Technical Services Manager / Infrastructure Team
Chose Qlik Replicate
I have not evaluated any other competing products. Qlik Replicate was the first product we selected for the data lake three years ago, and we have stayed with it ever since.
Fivetran, Stitch, and Etleap are all 1000x more modern than SSIS and 100x less aggravating. While those tools are mainly used to sync data rather than transform it, the ELT model works much better than the ETL model in most situations.
We just selected SSIS because we use SQL Server Management System (SSMS) to manage our database. As SSIS is a component of the Microsoft SQL Server there are no problems with integration and everything works perfectly. In addition, we don't have to learn how to use another …
Low-cost relative to other products - in fact, zero cost if one is considering the license cost as being for the database engine with Integration Services added on. It has a comparable range of functionality and performance and as such it's a 'no-brainer' to use SSIS over …
SnapLogic and Azure Data Factory are better than SQL Server Integration Services mostly because they are Integration Platform as a Service (IPAAS) services, whereas SQL Server Integration Services is an on-premise. So the basic differences such as, need a VPN to connect to the …
SSIS is similar to Alteryx and Informatica PowerCenter in a way because these are all drag-and-drop ETL tools with similar functionality. Alteryx is a step ahead because it has some advanced ETL functionalities including statistical calculations etc. and a better ability to set …
Alteryx Designer is easier to use for machine learning models. The functionality of drag and drop is the most valuable. It is a very user-friendly tool that can be understood easily. My teams also work with other solutions, such as Integration Services, and these solutions are …
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 …
SAP Business Objects was a primary concurrent software against the MS SSIS but it has a more steep learning curve and requires additional investment into the SAP-related software infrastructure. With SSIS one can start easily with simple data extraction / DTL tools of Express …
I personally prefer SSIS. There are items that each do better than the others, but the ease of use of SSIS, along with its extensibility to 3rd party, ability to write any code required in the tool, and uses the same IDE for the MS BI suite (more of an issue if you're not a …
I used the Pentaho Data Integration (PDI) ETL tool. The PDI ETL tool does not have a public user collection like the SQL Server Integration Services(SSIS) ETL tool. Therefore, you may not be able to find instant solutions for your problems. But it has advantages over the SSIS …
SQL Server is already in our wheelhouse so it only made sense to utilize the tools we already had available to us--SSIS, SSAS, & SSRS. Other non-technical users seem to be more comfortable using alternatives to SSIS. However, these alternatives are not as good as SSIS at …
These are all great products and, honestly, can move data faster. They include more enterprise features and have some great qualities about each. However, they all cost a lot depending on the implementation you need. With SQL Server Integration Services, you do not have any …
When looking to evaluate different options, we looked first to the experience and software we had in-house that would accomplish the job. When assessing alternatives outside we were looking for the tool that would offer the most flexibility.
It’s basically a free tool and it has more features than anyone would ever need. If you look online for answers for SISS packages you will find a world of information that can cover almost any situation for your business. This tool can be used in any business and it provides …
SSIS is a very basic, developer-oriented ETL tool and while it lacks many of the nice UX features of its competitors it is a powerful tool that comes as a part of SQL Server and, in the hands of experienced developers with domain knowledge, can meet most organizations' ETL …
SSIS and Denodo differ in their approaches to ETL and Data integrations. SSIS is more affordable from a cost and licensing perspective (if you have Microsoft licensing), but Denodo is no slouch. If you go with Denodo, you are not creating data, there are pros and cons to …
SQL Server Integration Services does a good job for our SQL Server environments and was selected for that reason. For a SQL Server-only implementations, I would recommend SQL Server Integration Services. When we compared SSIS to other ETL providers against SQL Server, SSIS was …
SSIS has more configuration options and its smooth running GUI (in visual studio) makes implementation easier. It's ability to provide visual programming and allow users to input code for more complex logic and configuration gives users a great degree of flexibility.
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.
Qlik Replicate brought a great experience with respect to the ease of implementation and great UI. We had a software that was a blackbox for the team and was very hard to maintain. Qlik Replicate implementation helped us avoid dependency on one resource.
Global transformation and in-built functions are what I like in our project.
You can customize the conversion/transformation using a JSON file generated by Qlik Replicate, and it is very convenient.
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.
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.
SSIS is responsible for running core business processed managing core business data. It can be managed, improved and expanded using minimal internal resources. It is also able to support all of our current data infrastructure. Replacing SSIS would be time consuming and costly with no apparent ROI.
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.
SSIS has a drag and drop based developer interface, so it is relatively straight forward to get started. You can start to get into the weeds pretty quickly as your solution becomes more complex. However, most of the base functions are right in front of you for a developer. You can also set project and solution level parameters, so when you deploy to new environments, you don't have to jump into each package to change your variables and settings. (For example, default directory to ingest flat files).
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 think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
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.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.