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 6.6 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
CData Sync
SQL Server Integration Services
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CData Sync
SSIS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
CData Sync
SQL Server Integration Services
Features
CData Sync
SQL Server Integration Services
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
CData Sync
-
Ratings
SQL Server Integration Services
7.5
53 Ratings
11% below category average
Connect to traditional data sources
00 Ratings
8.853 Ratings
Connecto to Big Data and NoSQL
00 Ratings
6.240 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
CData Sync
-
Ratings
SQL Server Integration Services
8.1
53 Ratings
1% below category average
Simple transformations
00 Ratings
8.553 Ratings
Complex transformations
00 Ratings
7.752 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
CData Sync
-
Ratings
SQL Server Integration Services
7.4
51 Ratings
7% below category average
Data model creation
00 Ratings
8.627 Ratings
Metadata management
00 Ratings
7.133 Ratings
Business rules and workflow
00 Ratings
8.242 Ratings
Collaboration
00 Ratings
7.338 Ratings
Testing and debugging
00 Ratings
6.148 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
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 if the company is already a Microsoft shop, so chances are that it is free with SQL Server. Also, good for moving data between on premise systems. Not ideal for moving data to the cloud. No functionality out of the box to work with REST APIs. Stable product but definitely not the future
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.
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.
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.