CloverDX Designer vs SSIS comparison

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

"It's something I needed for bulk imports. I'm not a big fan of it, but I haven't seen anything better."

"Data Flows are the main component we use. These can range from a simple source to sink ETL, to many source to many sink dataflows."

"Its compatibility with Microsoft products has been very valuable to our company. It fits well within the architecture."

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

"Despite the complexity when dealing with advanced transformations, it is straightforward for simple data movements, and the performance is excellent."

"The performance and stability are good."

"The most valuable feature of SSIS is that it can handle real complex transformations."

"The most valuable features for our company are the flexibility and the quick turn around time in producing simple ETL solutions."

"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."

"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."

"It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well."

"SSIS has a difficult learning curve when dealing with complex transformations."

"We're in the process of switching to Informatica, and we need to work out data lineage and data profiling and to improve the quality of our data. SSIS, however, is not that compatible with Informatica. We managed to connect it to Informatica Metadata Manager, but we don't get good lineage, so we have to redo all our ETLs using the Informatica process in order to accept the proper data lineage."

"I would also like to see full integration with our BI because then our full load of data will be available in our organization. They should incorporate an ATL process."

"The security could be improved, as it is more important in our context."

"The creation of the measure in the DAC's model could be improved."

"It would be nice if you could run SSIS on other environments besides Windows."

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

"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."

"t's incredibly cost effective, easy to learn the basics quickly (although like all ETL tools requires the traditional learning curve to get good at) and has an immense user base."

"Depending on the arrangement that a certain company has with Microsoft, it may supply the permanent license that is included in the SQL server license, or it may be a time-bound license if it is a partner license or other enterprise license."

"It would be beneficial if the solution had a less costly cloud offering."

"Based on my experience and understanding, Talend comes out to be a little bit expensive as compared to SSIS. The average cost of having Talend with Talend Management Console is around 72K per region, which is much higher than SSIS. SSIS works very well with Microsoft technologies, and if you have Microsoft technologies, it is not really expensive to have SSIS. If you have SQL Server, SSIS is free."

"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."

"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."

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