We performed a comparison between Qlik Compose and SSIS based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"It can scale."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"I have found it to be a very good, stable, and strong product."
"It's a stable solution."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"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."
"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."
"The most valuable feature of SSIS is its ease of use. It is easier to use than other applications."
"The performance is good."
"It has the ability to be deployed into the cloud through Data Factory, and run completely as a software as a service in the cloud."
"Like most Microsoft products, SSIS is user-friendly and easy to use."
"It's something I needed for bulk imports. I'm not a big fan of it, but I haven't seen anything better."
"SSIS' best feature is SFTP connectivity."
"The most valuable feature of SSIS is that it can handle real complex transformations."
"The data reader is the most valuable feature."
"I'd like to have access to more developer training materials."
"Qlik's ETL and data transformation could be better."
"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."
"There is some scope for improvement around the documentation, and a better UI would definitely help."
"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."
"There could be more customization options."
"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."
"I believe that visual data flow management and the transformation function should be improved."
"SSIS is stable, but extensive ETL data processing can have some performance issues."
"In terms of its performance, it could be better. That could be something that would be easy and welcomed as an upgrade."
"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."
"You have to write push down join & lookup SQL to the database yourself via stored procedures or use of the SQL Task to get very high performance. That said, this is a common complaint for nearly all ETL tools on the market and those that offer an alternative such as Informatica offer them at a very expensive add-on price."
"There are a lot of things that Microsoft could improve in relation to SSIS. One major problem we faced was when attempting to move some Excel files to our SQL Server. The Excel provider has a limitation that prevents importing more than 255 columns from a particular Excel file to the database. This restriction posed a significant issue for us."
"SSIS is cumbersome despite its drag-and-drop functionality. For example, let's say I have 50 tables with 30 columns. You need to set a data type for each column and table. That's around 1,500 objects. It gets unwieldy adding validation for every column. Previously, SSIS automatically detected the data type, but I think they removed this feature. It would automatically detect if it's an integer, primary key, or foreign key column. You had fewer problems building the model."
"This solution needs full support for real-time processing."
"I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use."
Qlik Compose is ranked 18th in Data Integration with 12 reviews while SSIS is ranked 2nd in Data Integration with 69 reviews. Qlik Compose is rated 7.6, while SSIS is rated 7.6. The top reviewer of Qlik Compose writes "Easy matching and reconciliation of data". On the other hand, the top reviewer of SSIS writes "Maintaining the solution and contacting its support team is easy". Qlik Compose is most compared with Qlik Replicate, Talend Open Studio, Oracle Data Integrator (ODI), Azure Data Factory and WhereScape RED, whereas SSIS is most compared with Informatica PowerCenter, Talend Open Studio, IBM InfoSphere DataStage, Oracle Data Integrator (ODI) and AWS Glue. See our Qlik Compose vs. SSIS report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
