SQL Server Integration Services Reviews and Ratings

Use Cases and Deployment Scope

Data Engineering and integration. Move data between different on-premise servers no matter the platform. Since we have an Enterprise Agreement with Microsoft, it does not cost any extra to use SQL Server Integration Services unlike Azure Data Factory or Informatica. Wherever data transfer is involved, it is the de-facto standard in our company.

Likelihood to Recommend

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

Use Cases and Deployment Scope

SSIS pulls data from various locations (mostly SQL Server instances but also some flat files and SFTP), mainly for transforming the data and putting it in the data warehouse.

Likelihood to Recommend

If you already have licenses for SQL Server and need to get data from A to B, especially if A and/or B is SQL Server, then SSIS could be a reasonable choice, especially if you can't use a cloud tool like Fivetran due to security concerns.

Use Cases and Deployment Scope

SQL Server Integration Service (SSIS) is a component of the Microsoft SQL Server database software that we use to execute a wide range of data migration tasks. SSIS is a fast & flexible data warehousing tool used for data extraction, loading, and transformation like cleaning, aggregating, merging data, etc. It makes it easy to move data from one database to another database. SSIS can extract data from a wide variety of sources like SQL Server databases, Excel files, Oracle and DB2 databases, etc.

Likelihood to Recommend

<ul><li>SSIS is an in-memory pipeline. That’s why it’s important to make sure that all transformations occur in memory</li><li>Try to minimize logged operations</li><li>Plan for capacity by understanding resource utilization</li><li>Optimize the SQL lookup transformation, data source, and destination</li><li>Schedule and distribute it correctly</li></ul>

Use Cases and Deployment Scope

We use SQL Server Integration Services (SSIS) as part of our on-premise Data Warehouse architecture. We have an ELT pattern and SSIS is used almost exclusively for the Extract and Load steps. Almost all packages are generated using BIML (Business Intelligence Markup Language) as a means of templating and then scripting them.

Likelihood to Recommend

I do not think that SQL Server Integration Services (SSIS) is great for complex dependency management and scheduling for an entire DW load. However, it is great for smaller units of work and particularly where moving data between systems is required due to its extensive and extensible connectivity options. That said, it is obviously focused on traditional on-premise systems and cloud-based environments are likely to prefer using the next-generation version of SSIS being Azure Data Factory (ADF).

Use Cases and Deployment Scope

SSIS is an on-premise data transformation tool and the first major ETL tool we have used. We use it to ETL data from Workday, and other internal applications/databases to our internal databases. The product addresses the issue of getting data from CSV files from our SFTP and performing update/insert/delete operations on the data in our internal databases.

Likelihood to Recommend

SQL Server Integration Services is well suited for anyone beginning to learn ETL. It's a great tool, to understand the nuances of setting data integrations and transformations. SQL Server Integration Services is not meant for ELT or ETLTL operations, natively. The workaround would be to have multiple packages/pipelines where one package performs the EL and the other package performs the T.

Use Cases and Deployment Scope

We are currently using SQL Server as our central relational database. Getting data from multiple sources to our data depository is smooth. We use SQL Server Integration Services to copy and download large files as well as to draw out and modify data from several sources of data like XML data files, DB2 databases, and relational data sources and then load the data into a single destination.

Likelihood to Recommend

We have used SSIS to perform extensive data migration tasks from various sources like DB2 databases, SQL server databases... It works speedily making it easy for us to move data from one database to the other. It also has a GUI that helps us extract, transform, and clean data easily without writing code. It works well except for the error messages.

Use Cases and Deployment Scope

SQL Server is the legacy Database and Data Warehouse in the company. SSIS is used for most ETLs where the data is sourced from / put into SQL Server, depending on the use case. It is an MS native and easy-to-use ETL tool that comes with the SQL Server Data Tools suite. I use the tool personally to deploy ETLs for business stakeholders as a request arises.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

A good tool for SQL server query and data migration. The way it stores data and makes it easier for the user to write queries over the server. Compatibility with different BI tools is awesome as it is easy to integrate Microsoft SQL servers with different BI tools like google data studio and PowerBI.

Likelihood to Recommend

1. Combining and integrating data from a variety of sources.

2.There is no additional necessity to learn anything other than SQL.

3. Assists in the analysis of client data by bringing it all together in one place.

4. Data leaks of clients' personal information are avoided. It is HIPAA compliant and it has very secure server.

Use Cases and Deployment Scope

Microsoft's SQL Server Integration helps in keeping a track of our data dump in a suitable &amp; orderly manner. The service not only helps in making sure the data is readily available but it also helps in bifurcating the data according to our needs &amp; requirements. The data is quickly available when needed &amp; helps in our workings on a daily basis.

Likelihood to Recommend

The service is very well suited if you want to integrate various data sources spread across the cloud &amp; compile all that data in one place effectively &amp; quickly. The service can use a little work in connecting to multiple data sources over the cloud at one go &amp; struggles if too many data connections are used together.

Use Cases and Deployment Scope

In our organization, we have two Microsoft windows servers. We integrate their data sync via SQL Server Integration Services. It's easy for us to migrate our data from one server to another server. The debugging capabilities are great, particularly during data flow execution. We can look into the data and see what's going on in the pipeline.

Likelihood to Recommend

Helpful in connecting to various data sources and loading the combined data. More cost-efficient than other ETL tools of the same stature. Reduces the need for coding scripts.