CData's Sync is a data pipeline tool able to connect data sources to the user's database or data warehouse, supporting at present over 200 possible sources, and a range of destinations (e.g. Snowflake, S3, Redshift), connecting on-premise or SaaS sources and destinations.
N/A
SSIS
Score 8.0 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
Evidently, CData Sync is an excellent middleware tool that is perfect for syncing data between systems. It is especially suitable and works well on SQL servers, DB2, MySQL, and Snowflake, and some of their brothering domains. However, it is a limitation in working with Sage 50 API. But if it is extracted with ODBC, it works well.
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.
Although efficient for SQL servers and MySQL, as well as Snowflake. It is not strong for other database engines, and an upgrade on this would do a lot.
The installation process is manual as opposed to the cloud installation it should be.
A feature of syncing auto increment ID key, that will help in existing data management.
SSIS has been a bit neglected by Microsoft and new features are slow in coming.
When importing data from flat files and Excel workbooks, changes in the data structure will cause the extracts to fail. Workarounds do exist but are not easily implemented. If your source data structure does not change or rarely changes, this negative is relatively insignificant.
While add-on third-party SSIS tools exist, there are only a small number of vendors actively supporting SSIS and license fees for production server use can be significant especially in highly-scaled environments.
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
SQL Server Integration Services is a relatively nice tool but is simply not the ETL for a global, large-scale organization. With developing requirements such as NoSQL data, cloud-based tools, and extraordinarily large databases, SSIS is no longer our tool of choice.
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 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
Tableau is another similar software tool, unlike CData Sync, rather transforms data into actionable insights. While CData Sync works with automation, Tableau uses a drag box on its AVA, which in turn slows the work speed on the syncing of data. Over the years, I enjoyed the friendly and customizable option of CData Sync over Tableau's.
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.
