SSIS 2025 Version Expert

Configuration: In the ADO.NET connection manager, select "Microsoft SqlClient Data Provider" as the provider. Set authentication method in the connection string (e.g., Authentication=Active Directory Interactive or Authentication=Active Directory Service Principal).

This is the only new feature in SSIS 2025. The emphasis is on making existing packages compatible with modern security infrastructure.

Deprecated Features

Removed Features

Breaking Changes

Microsoft.SqlServer.Management.IntegrationServices Assembly

This managed API assembly now depends on Microsoft.Data.SqlClient instead of System.Data.SqlClient. This potentially breaks:

• Existing PowerShell deployment scripts that create System.Data.SqlClient.SqlConnection objects
• Custom .NET applications using the SSIS managed API
• Automated CI/CD pipelines that deploy via the IntegrationServices assembly

Fix: Update connection creation code to use Microsoft.Data.SqlClient.SqlConnection and add the Microsoft.Data.SqlClient NuGet package to custom projects.

Execute SQL Task and SMO-Dependent Tasks

• Projects using Microsoft.SqlServer.Dts.Runtime namespace with Execute SQL Task or SMO-dependent tasks must update references and rebuild
• Maintenance tasks using the SqlClient Data Provider connection type must switch to ADO.NET

32-bit Provider Dependencies

• Packages relying on 32-bit-only providers (Jet/ACE for Excel/Access) will fail at runtime
• No Run64BitRuntime = false workaround in SSIS 2025 tooling
• Must install 64-bit providers or redesign connections (CSV, database staging)

Future Direction Signals

SSIS 2025 carries significant signals about Microsoft's strategic direction:

1. Announced on the Microsoft Fabric Blog, not the SQL Server blog
2. One new feature, many removals: Security modernization only; no engine improvements
3. Fabric bridge: Invoke SSIS Package activity in Fabric pipelines (preview) for lift-and-shift
4. No EOL announced: SQL Server 2025 will have standard Microsoft lifecycle (mainstream + extended support)
5. Practical interpretation: SSIS is in maintenance mode; new investment goes to Fabric

Migration Notes

From SSIS 2022

1. Audit packages for removed components: Attunity CDC, Oracle connector, Hadoop tasks -- must replace before upgrading
2. Audit 32-bit dependencies: Any package using Run64BitRuntime = false or 32-bit-only providers needs remediation
3. Update deployment scripts: If using PowerShell or .NET with Microsoft.SqlServer.Management.IntegrationServices, update to Microsoft.Data.SqlClient
4. Test thoroughly: The assembly dependency change can surface in unexpected ways during deployment automation
5. Update connection types: Replace SDS connection type in maintenance tasks with ADO.NET

Upgrade Checklist

• Inventory all packages for Attunity CDC, Oracle connector, Hadoop task usage
• Identify packages using 32-bit execution mode or 32-bit-only providers
• Test deployment scripts with the new Microsoft.Data.SqlClient dependency
• Verify all connection managers work in 64-bit mode
• Update TargetServerVersion in project properties to SQL Server 2025
• Test in non-production SSISDB before production deployment
• Plan migration timeline for packages using deprecated features
• Evaluate Entra ID authentication for Azure SQL / Fabric connections

New Project Guidance

For new projects on SQL Server 2025, consider whether SSIS is the right choice:

• Use SSIS if: On-premises requirement, existing SSIS expertise, complex visual data flows, SQL Server-centric environment
• Consider alternatives if: Cloud-first architecture, new team with no SSIS experience, real-time requirements, cross-platform needs
• Recommended alternatives: Azure Data Factory, Microsoft Fabric Data Pipelines, Apache Airflow