If your back end RDBMS is SQL Server, SSIS gives you a bang for your buck.
April 27, 2018

If your back end RDBMS is SQL Server, SSIS gives you a bang for your buck.

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with SQL Server Integration Services

SSIS was being used as an ETL tool both by IT as well as business teams. It is now replaced by a competitor though. The tool was being used for basic extraction and loading purposes, with hardly any complex data transformation being done. Though there were use cases to exploit the tool, neither Microsoft nor in-house consultants really helped with the tool, with the result being it getting replaced.
  • Source systems connectivity (RDBMS, Flat Files etc)
  • Embedding SQL and other code in case of complex business logic and data transformations
  • Multitude of data transformation options
  • Ease of use, easy to learn
  • Skills availability in the market
  • version control/configuration management
  • Programmatic issues like NULL handling (it's RDBMS counterpart SQL Server database uses NULL differently)
  • The source connectivity options should be enhanced
  • It wasn't used effectively, resulting in not realising ROI to the extent we had anticipated
  • It was easy to learn, which resulted in business teams using it extensively without IT support, resulting in lots of packages/code to maintain
Selection was done because of: 1. Lower Cost, 2. RDBMS was SQL Server and SSIS is tightly coupled for optimal performance
If the back end RDBMS is SQl Server and if you are migration from Oracle or DB2 to SQL Server, SSIS does the migration job very well. It's tightly integrated with SQL Server. However, issues like NULL handling etc persists. Also, if the integration platform has unsupported connectivity or drivers, then SSIS usage becomes challenging.

SSIS Feature Ratings

Connect to traditional data sources
Connecto to Big Data and NoSQL
Simple transformations
Complex transformations
Metadata management
Testing and debugging
Integration with data quality tools
Integration with MDM tools

Using SQL Server Integration Services

250 - Predominantly IT besides other business functions
  • Simple extraction and loading
  • self service data integration
  • complex transformations
  • None, with the version it was then
A bit outdated compared to competitors, esp in the open source community

Evaluating SQL Server Integration Services and Competitors

  • Price
  • Product Features
  • Product Usability
  • Existing Relationship with the Vendor
Cost, back end RDBMS being SQL Server
Things have changed now and there are more use cases to consider than what we had considered years ago. It's a different ball game now. We might do it grounds up this time

SQL Server Integration Services Support

They are generally responsive and knowledgeable too
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Support understands my problem
Support cares about my success
Quick Initial Response
Difficult to get immediate help

Using SQL Server Integration Services

Easy to use, however there are functionality limits
Relatively simple
Easy to use
Technical support not required
Well integrated
Quick to learn
Do not like to use
  • Pretty much everything is easy to use
  • complex transformations which SSIS can't really handle