CloverDX Designer vs SSIS comparison

"Its simplicity and the way it handles graphs are the most valuable features."

"The setup is easy to use and understand."

"We like that this solution includes a developer edition, free of charge, to allow for training."

"The performance is good."

"Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools."

"The solution is stable."

"The simplicity of the solution is great. The solution also offers excellent integration."

"The most valuable features of SSIS are that it works with the query language and it can import data from different sources."

"The most valuable feature of SSIS is that you can take data from other servers which are not MS SQL Server or Oracle."

"If I could give any advice to the guys who are developing it, I would suggest them to really look at the enterprise features, such as being able to log what's going on, being able to capture the current state of processing, and being able to recover from error situations. So, there should be a focus on logging, recoverability, and monitoring. We should be able to monitor what's going on, and in case of any issues, we should be able to recover and restart processing and other things. For scalability and performance, I would probably suggest the Pushdown feature so that you can do the transformation directly on the data source. You do not need to do that calculation within the ETL server. For this, you should be aware of the type of data because each database or kind of storage, such as Hadoop, has its own ANSI standard or language, such as SQL. Microsoft, Oracle, and IBM have their own language. Based on the feedback that I have got, its initial setup takes some time. It could perhaps be simpler."

"The solution could improve on integrating with other types of data sources."

"Microsoft should offer an on-premises support warranty for those using that deployment. They seem to be withdrawing from on-premises options."

"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."

"There were some issues when we tried to connect it to data storage. It was a connection issue."

"It needs more integration tools, so you can connect to different sources."

"Video training would be a helpful addition."

"It's difficult to refactor SSIS. It gets cumbersome to reuse the solution."

"We In upgrading SSIS, we encountered challenges fixing SQL Server and performance issues, including problems during a failover in our data warehouse."

"Its price and value for money would be okay for our purpose if there were some additional features."

"This solution has provided an inexpensive tool, and it is easy to find experienced developers."

"I'm not involved in licensing details, but SSIS provides value to our organization by simplifying data management tasks."

"If you don't want to pay a lot of money, you can go for SSIS, as its open-source version is available. When it comes to licensing, SSIS can be expensive."

"This solution is a free of charge addition to our SQL licence. However, the only way this tool can be utilized is as a feature of the SQL licence, which may make it unattractive to organizations who don't wish to purchase the wider-ranging licence."

"The solution is available at a lesser price than that of Informatica."

"The solution is economical. You don't have to worry about the pricing as long as you're installing both services on the same server."

"This solution is included with the MSSQL server package."

"SSIS' licensing is a little high, but it gives good value for money."