SQL Server Integration Services (SSIS) has long been a cornerstone of enterprise data movement and transformation. As businesses increasingly rely on data-driven decision-making, SSIS continues to evolve, offering robust tools for Extract, Transform, Load (ETL) operations. Among the various iterations of SSIS, the version labeled “SSIS 950” has sparked curiosity, often leaving developers and DBAs wondering: what exactly does “950” mean? What features does it signify? How does it align with SQL Server 2019?
This blog post will demystify SSIS 950, unpack its technical meaning, explore its features, and help you understand its importance within the SSIS ecosystem.
What is “SSIS 950”?
At first glance, SSIS 950 might sound like a product version number, but it refers to the PackageFormatVersion used internally by Integration Services. When you save an SSIS package in SQL Server Data Tools (SSDT), it includes a PackageFormatVersion attribute that corresponds to a specific SQL Server version.
In this case:
- SSIS 950 = PackageFormatVersion 9.50
- This corresponds to SQL Server 2019
Therefore, when someone refers to “SSIS 950,” they’re talking about SSIS packages built and targeted for SQL Server 2019.
A Brief History of SSIS Package Versions
To fully understand SSIS 950, let’s look at how PackageFormatVersion has changed across SQL Server versions:
| SQL Server Version | SSIS Version | PackageFormatVersion |
|---|---|---|
| 2005 | SSIS 2005 | 2 |
| 2008 / 2008 R2 | SSIS 2008 | 3 |
| 2012 | SSIS 2012 | 6 |
| 2014 | SSIS 2014 | 8 |
| 2016 | SSIS 2016 | 8.0+ |
| 2017 | SSIS 2017 | 8.0+ |
| 2019 | SSIS 2019 | 9.50 (SSIS 950) |
| 2022 | SSIS 2022 | 10.0+ |
Thus, SSIS 950 specifically identifies packages created or upgraded to target SQL Server 2019.
How to Identify SSIS 950 Packages
If you’re working with .dtsx files (SSIS packages stored in XML format), open the file in a text editor and look for:
xmlCopyEdit<DTS:Package ... PackageFormatVersion="950" ... >
This means it’s an SSIS 2019 package, using features and compatibility exclusive to SQL Server 2019.
You can also check this in SQL Server Data Tools (SSDT) or Azure Data Studio, where the package properties may reflect the target SQL Server version.
Key Features of SSIS 950 (SQL Server 2019)
SSIS 950 inherits and extends many of the powerful features from previous versions, while adding enhancements tailored for modern enterprise data pipelines. Some of the most noteworthy features include:
1. Improved Azure Support
SQL Server 2019 makes cloud integration a priority. SSIS 950 comes with better support for:
- Azure Data Lake Storage Gen2
- Azure Blob Storage
- Azure SQL Database
- Integration Runtime for running SSIS packages in Azure Data Factory (ADF)
This means developers can build hybrid ETL pipelines that run on-premises and in the cloud with minimal friction.
2. Scale-Out Enhancements
SSIS Scale-Out was first introduced in SQL Server 2017, and in SQL Server 2019 (SSIS 950), it is more stable and easier to configure. With this:
- You can run SSIS packages in parallel across multiple nodes.
- SSIS Catalog (SSISDB) supports Scale-Out configuration natively.
- Built-in logging and monitoring for Scale-Out workers is enhanced.
This is ideal for enterprises processing large volumes of data across clusters.
3. SSISDB Improvements
SSIS 950 improves the Integration Services Catalog (SSISDB) in several ways:
- Retention of historical logs and execution details is now configurable.
- Performance improvements when deploying or validating packages.
- Package execution reports are more detailed.
These improvements help DBAs monitor, troubleshoot, and manage packages more effectively.
4. Data Flow Performance Boost
SSIS 950 offers better performance in data flows thanks to:
- Enhanced thread management
- Optimized memory usage
- Improved transformations like Lookup, Merge Join, and Aggregate
For large data sets, these enhancements can significantly reduce execution time.
5. Custom Setup for ODBC / ADO.NET
In SSIS 950, Microsoft improved support for newer data providers, making it easier to use:
- ODBC connections with parameterized queries
- ADO.NET with additional data types
- Enhanced connectivity to PostgreSQL, MySQL, and Oracle via new drivers
6. SSIS Projects in Visual Studio 2019
SSIS 950 packages are best edited and deployed using:
- SQL Server Data Tools (SSDT) for Visual Studio 2019
- Targeting SQL Server 2019 Integration Services
Be sure your SSIS project is set to target SQL Server 2019 to utilize these features.
Migration Considerations: Upgrading to SSIS 950
Upgrading your existing SSIS packages to the 950 format involves careful planning. Here are some key steps:
1. Backup Existing Packages
Always retain copies of original packages before migrating. Once saved in 950 format, they are not backward-compatible.
2. Upgrade the Project Target Version
In SSDT:
- Open your SSIS project.
- Go to project properties → Configuration Properties → General.
- Set the TargetServerVersion to SQL Server 2019.
This triggers the automatic conversion of all packages in the project to PackageFormatVersion 950.
3. Validate and Test
Post-upgrade, validate each package and run test executions to ensure that components behave as expected. Pay particular attention to:
- Script Tasks (which might require recompiling)
- Connection Managers (especially for legacy or 3rd-party connectors)
- Expressions and variables
Deployment Options for SSIS 950 Packages
SSIS 950 packages can be deployed using various methods:
1. SSIS Catalog (SSISDB)
The recommended method. Use Project Deployment Model to deploy packages to SSISDB on SQL Server 2019. Benefits include:
- Centralized storage
- Parameterization
- Logging and history
- Integration with SQL Agent Jobs
2. Azure-Enabled Deployment
Use Azure Data Factory’s Integration Runtime to:
- Run SSIS 950 packages in the cloud
- Schedule and monitor package execution from Azure
- Integrate SSIS pipelines with Data Factory workflows
3. Command Line or PowerShell
Using utilities like dtutil.exe, dtexec.exe, or PowerShell scripts, you can deploy and execute packages from CI/CD pipelines.
Troubleshooting SSIS 950
While SSIS 950 brings many enhancements, developers may still face challenges. Common issues include:
a. Missing Components or Drivers
Ensure all required components (like Oracle connectors, Excel drivers) are installed on the server executing the package.
b. Script Task Compilation Errors
If you upgrade a package with a Script Task, the embedded code may need to be recompiled or rewritten to be compatible with .NET Framework used in VS 2019.
c. Connection Manager Failures
Some older connection strings or credentials may not migrate cleanly. Re-test all connections after conversion.
SSIS 950 in CI/CD and DevOps Workflows
Modern teams leverage CI/CD practices to automate SSIS deployments. With SSIS 950, you can:
- Use MSBuild to build SSIS projects
- Use Azure DevOps pipelines to deploy .ispac files to SSISDB
- Leverage SSDT project files with source control (e.g., Git)
This brings SSIS into the DevOps era, enabling agile data integration.
Conclusion
SSIS 950, the internal format version for SQL Server 2019 Integration Services, represents a mature, scalable, and cloud-friendly ETL platform. With enhancements in Azure integration, Scale-Out capabilities, and performance, SSIS 950 is ideal for modern enterprise data workflows.
Understanding the significance of “SSIS 950” helps organizations plan upgrades, maintain compatibility, and harness the full power of SQL Server 2019’s data transformation capabilities. Whether you’re deploying packages on-prem, in the cloud, or in a hybrid setup, SSIS 950 offers the flexibility, performance, and tooling support to meet your needs.
Pro Tip: Before migrating all packages to SSIS 950, create a development sandbox to test compatibility, performance, and feature adoption. Once confident, begin phased production rollout.
Would you like a downloadable checklist for upgrading SSIS projects to 950 format?
