CloverDX is a rapid, end-to-end data integration solution. The vendor states that businesses choose CloverDX for its usability and intuitive controls, along with its lightweight footprint, flexibility, and processing speed. Achieving true, rapid data integration means much more than just raw data processing power. Rapid refers to an end-to-end process that begins the moment a data-related problem is recognized to the point when the data is in the right place and form to be analyzed and…
N/A
SSIS
Score 8.2 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
CloverDX designer as a standalone is well suited for fairly straightforward transformations of data. If you want to do large scale data integrations, then their server edition adds an extra level of automation and job control.
There are always alternative options available to meet the demand for integration. In my opinion, SQL Server Integration Services has a wide variety of capabilities that makes it a very versatile tool for developing dependable integration strategies. When determining which tools to utilize, vendor interfaces may play a significant role, and technologies like PowerShell have been used by colleagues to aid in this decision. For even more user-friendliness, our SSIS solution additionally makes use of a third-party plugin.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
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
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
While CloverDX has an active forum for users to submit questions and assist with answers, their in house support team is incredibly responsive when I've contacted them for assistance. This seems almost at odds with most other software companies who try to save money on tech support by promoting a forum or knowledge base.
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.
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
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.
Work that use to take multiple people 20 to 30 hours a week to complete each has now been fully automated to where only 1 or 2 hours a week for maintenance is required.