---
title: "SSIS | Skills We Assign For | Azendo"
description: "SSIS in Microsoft data estates — inherited packages, deployment, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/ssis/"
---

[Skills](https://azendo.co/skills/) Data pipelines 

# SSIS.

SQL Server Integration Services is Microsoft's ETL platform, building data flow packages in a visual designer and executing them on SQL Server. It is present in most long-running Microsoft data estates.

## Where SSIS fits on a long engagement.

SSIS packages are the plumbing of most established Microsoft estates, and they are almost always undocumented. A package built years ago moving data between systems, scheduled through SQL Agent, still running correctly, with nobody who can explain the transformations inside it, is the standard situation rather than the exception.

The packages are usually still the right answer for what they do. They work, they are integrated with the estate, and rewriting them elsewhere is cost without benefit unless something specific forces it. The productive work is understanding them, testing them, and monitoring them properly.

## What an assigned team does with SSIS.

Failure handling is the common gap. Many inherited packages fail silently or log only to a table nobody watches, which means a load that stopped three days ago is discovered when a report is wrong.

Adding real alerting to existing packages is small work with a large reliability return, and it sits inside the standing capacity described in [how an assignment runs](https://azendo.co/how-it-works/).

## What we use SSIS for.

* Inherited packages understood Transformations documented, because the package is often the only record of the rules.
* Failures that are noticed Alerting added, so a stopped load is known within minutes rather than days.
* Deployment brought into version control Packages managed as artefacts rather than edited in place on a server.

## How SSIS capacity is assigned.

SSIS capacity is assigned under [managed data services](https://azendo.co/services/data-engineering/), with monitoring added to inherited packages before any modernisation is considered.

## Roles we assign SSIS for

* [ETL Developer Data engineering](https://azendo.co/services/data-engineering/etl-developer/)

## Service lines it sits in

* [Data engineering](https://azendo.co/services/data-engineering/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in data pipelines

* [Talend — skill we assign for](https://azendo.co/skills/talend/)
* [Change data capture — skill we assign for](https://azendo.co/skills/change-data-capture/)
* [incremental loads — skill we assign for](https://azendo.co/skills/incremental-loads/)
* [data modelling — skill we assign for](https://azendo.co/skills/data-modelling/)
* [dimensional design — skill we assign for](https://azendo.co/skills/dimensional-design/)
* [star schema and dimensional modelling — skill we assign for](https://azendo.co/skills/star-schema-and-dimensional-modelling/)
* [slowly changing dimensions — skill we assign for](https://azendo.co/skills/slowly-changing-dimensions/)
* [version-controlled transformations — skill we assign for](https://azendo.co/skills/version-controlled-transformations/)

## Tell us what your roadmap needs SSIS for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)