Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Veeam Backup for Google Cloud Platform
Score 10.0 out of 10
N/A
Veeam Backup for Google Cloud Platform automates Google-native snapshots to securely protect VMs across projects and regions with ultra-low RPOs and RTOs, and store backups in Google Object Storage to enhance data protection (because snapshots alone are never enough). The vendor states this ensures lower costs for long-term retention.
N/A
Pricing
SQL Server Integration Services (SSIS)
Veeam Backup for Google Cloud Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
SSIS
Veeam Backup for Google Cloud Platform
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
SQL Server Integration Services (SSIS)
Veeam Backup for Google Cloud Platform
Features
SQL Server Integration Services (SSIS)
Veeam Backup for Google Cloud Platform
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
SQL Server Integration Services (SSIS)
7.0
56 Ratings
16% below category average
Veeam Backup for Google Cloud Platform
-
Ratings
Connect to traditional data sources
9.056 Ratings
00 Ratings
Connecto to Big Data and NoSQL
5.043 Ratings
00 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
SQL Server Integration Services (SSIS)
6.8
56 Ratings
17% below category average
Veeam Backup for Google Cloud Platform
-
Ratings
Simple transformations
9.056 Ratings
00 Ratings
Complex transformations
4.755 Ratings
00 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
SQL Server Integration Services (SSIS)
7.5
54 Ratings
4% below category average
Veeam Backup for Google Cloud Platform
-
Ratings
Data model creation
9.028 Ratings
00 Ratings
Metadata management
6.035 Ratings
00 Ratings
Business rules and workflow
7.045 Ratings
00 Ratings
Collaboration
9.040 Ratings
00 Ratings
Testing and debugging
6.351 Ratings
00 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
Until now, it was not possible to back up the server and respond to emergencies, but with the introduction of this software, it is possible to go back. By supporting One Stop for various virtual OS environments, ease of use is greatly improved. Contributes to reduced TCO and high ROI by reducing management man-hours.
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
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
First and foremost, this solution fits better into the budget than either of the solutions above. Additionally, I think it suits the market I was in better than the other software that play better in a strictly SMB or Enterprise space. Overall, I think this is a niche product that fits well. It's a flexible product and one that can accomplish and provide value for you in whatever capacity you need at the moment.
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.