Press "Enter" to skip to content

Category: Integration Services

Microsoft.Data.SqlClient Connection error in SSIS 2025

Published 2026-06-16 by Kevin Feasel

Andy Leonard troubleshoots (with assistance from Claude) a tricky error:

Recently, I was developing an SSIS package that read from an Azure SQL DB table and wrote to an on-premises SQL Server 2025 database table. I encountered the following error:

[ADO NET Source [41]] Error: ADO NET Source has failed to acquire the connection {<ConnectionManagerGUID>} with the following error message: “Could not load file or assembly ‘Microsoft.Data.SqlClient, Version=6.0.0.0, Culture=neutral, PublicKeyToken=<PublicKeyToken>’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)”.

The issue has nothing to do with a missing file or assembly.

Leave a Comment

What’s New with the Fabric SSIS Preview

Published 2026-03-24 by Kevin Feasel

Andy Leonard frames the discussion:

The conversation around SSIS is heating up again.

Some see the signals and conclude SSIS is on the way out. Others point to the strength of the ecosystem and say it is far from done. Both perspectives miss something important.

The introduction of Fabric SSIS public preview does not settle the debate. It reframes it.

I see this as another way of saying, “We know you’re still using SSIS packages but we really don’t want to invest in that any longer, so how about you move it into Fabric until you do finally rewrite things as Fabric Data Pipelines?”

That said, Andy lays out where he sees the current landscape and how there are common issues across Microsoft’s ETL/ELT products, mostly in how people use them.

Comments closed

What’s New in SSIS 2025

Published 2026-03-05 by Kevin Feasel

Koen Verbeeck actually gets an article’s length out of this:

There’s a new version of SQL Server released and we’re mainly an on-premises SQL Server shop. We’ve been using Integration Services (SSIS) for years now for all our ETL and data integration needs. With Microsoft’s focus on cloud (Azure and Fabric), does it make sense to upgrade our SSIS packages? Are there any new features?

Click through for the answer, though “stuff that’s gone away” or “stuff that you have to change because of drivers” make up almost 100% of this.

Comments closed

Failure Tracking in SSIS

Published 2026-02-26 by Kevin Feasel

Andy Brownsword keeps a log:

SSIS packages provide great flexibility for integration between systems, but when they go wrong you can end up digging through logs or reports because every package logs differently. A standarised framework for tracking failures can drastically cut down troubleshooting time.

I reminisced recently about old code, I said “it’s not enough to make it work correctly. It needs to fail correctly too”. So in this post we’ll demonstrate a simple way to consistently track errors and failures in packages to help make troubleshooting much easier.

My recollection is that this kind of failure logging is less important if you have the SSISDB catalog, as it collects a lot of the information as well. But then again, I haven’t really used SSIS in a while, so that memory could be fuzzy.

Comments closed

Install and Configure SSIS 2025

Published 2026-02-06 by Kevin Feasel

Koen Verbeeck performs an installation:

We’re an on-premises shop running all our services on our own machines. We’re planning to migrate to SQL Server 2025 and there are some older SSIS projects we might need. Is SQL Server Integration Services still supported in SQL Server 2025? If yes, how can we install it on our server? Do we still need Visual Studio to develop projects and packages, and how can we convert the older projects?

Granted, SSIS hasn’t exactly changed a lot with SQL Server 2025, but it’s there for you.

Comments closed

Thoughts on the State of SSIS

Published 2026-01-05 by Kevin Feasel

Andy Leonard shares some thoughts:

At the outset of 2026, I live in two worlds.

I continue to support clients who use SSIS for enterprise data engineering. Some of the enterprises are small-ish by comparison. Others are huge. Some friends also continue to support these clients and clients like them. That’s World 1.

World 2 is social media. I have some friends on social media. Many I know IRL (in real life). Most, though? Most are acquaintances. Most of my interactions on social media are with people I don’t really know or don’t know that well. Conversely, many of them – of you – don’t know me that well, either. I touched on this in a recent newsletter / post titled 2025: A Number Containing Two 2’s, One 5, and a 0.

My biggest problem with SSIS is that Microsoft has almost zero real effort into it in the past decade, which makes me hesitant to use it anymore. Yeah, I have gripes about CI/CD—BIML resolved a lot of those for me, but I haven’t seen anybody talk about that topic in the past 8 or so years, either. Andy has done a lot of good stuff with his DILM suite as well, and there are some good third-party components that implement functionality Microsoft never got around to doing. But at the end of the day, how long does Microsoft continue to “support” SSIS, and at what point does this become a corporate risk?

Comments closed

What’s New in SSIS for SQL Server 2025

Published 2025-12-15 by Kevin Feasel

Chunhua Gu says, not much:

Security is a top priority for SSIS 2025, reflecting the broader enterprise’s focus on data protection and compliance. Microsoft.Data.SqlClient provides a modern, secure data access layer. This new provider supports advanced security protocols, including TLS 1.3 for encrypted connections, and integrates seamlessly with Microsoft Entra ID (formerly Azure Active Directory) for robust authentication.

In short, support the new-ish library (that has been around for several years), tie in with Microsoft Fabric, remove functionality that used to be in the product while spinning this as a grand new opportunity for developers to spend money on Fabric, and that’s it. Granted, SSIS hasn’t been a proper focus for the product since 2012 (sorry, Hadoop components in 2016—you’re out of the product now, so you don’t count), so all of this should come at no surprise.

Comments closed

Using Python Code in SSIS

Published 2025-08-12 by Kevin Feasel

Tim Mitchell shoe-horns a language in:

SQL Server Integration Services (SSIS) is a mature, proven tool for ETL orchestration and data movement. In recent years, Python has exploded in popularity as a data movement and analysis tool. Surprisingly, though, there are no native hooks for Python in SSIS. In my experience using each of these tools independently, I’d love to see an extension of SSIS to naturally host Python integrations.

Fortunately, with a bit of creativity, it is possible to invoke Python logic in SSIS packages. In this post, I’ll walk you through the tasks to merge Python and SSIS together. If you want to follow along on your own, you can clone the repo I created for this project.

Honestly, it’s not that surprising. The last time there was significant development on Integration Services was roughly 2012 (unless you include the well-intentioned but barely-functional Hadoop support they added in around 2016). At that point, in the Windows world, Python was not at all a dominant programming language.

Comments closed

Tips for Solving SSIS Package Bottlenecks

Published 2025-08-12 by Kevin Feasel

Andy Brownsword has some advice:

Last time out we started to look at optimising SSIS packages by showing how to identify bottlenecks with a handy script. This time we’re turning insights into action to solve those pain points.

The solutions are grouped into 3 areas: Data Flows, as they do a lot of heavy lifting; the Execute SQL task, which can also be used for transformation and calculations; and finally everything else (because the first two are usually the issue).

Andy has some good advice and plenty of links to prior content around optimizing SSIS performance. One small thing I’d add is architectural: think about whether you can solve the slow part inside SQL Server. If you’re grabbing a huge amount of data from a SQL Server instance and then narrowing it down with filters, it might be a lot faster to transform that into a SQL query with a stronger WHERE clause. But let’s say there’s some small file you’re using to filter, so you need to pull all of the data out of SQL Server to compare against the small file so that you know what you need. Instead of pulling all of the data out of SQL Server or setting up a Lookup component to hit the SQL Server instance for each row in the file, how about loading that file into SQL Server and then writing a query to do the work?

In short, the database engine is typically going to be a much better at performance than an integration layer would be.

Comments closed