I am running out of ideas.

As this happens for only one query, there must be something about that query which is different from all the others. Is there anything special...

And are you using prepared statements?

https://learn.microsoft.com/en-us/dotnet/api/system.data.sqlclient.sqlcommand.prepare?view=net-9.0-pp

Does the query contain variables or parameters?

OK, understood. Is this a fundamental connection problem (ie, all queries time out), or is there just one particular query which is giving the issue?

You say it runs in seconds when run 'directly'. So presumably you are running it 'indirectly' – can you elaborate on that?

This sounds like the best idea, though obviously it will take some time to...

Yes, I saw that as well, but how are the sources different? The OP didn't...

The sources for the datasets are different, so I don't think that will work.

Assuming you have your SSIS solution checked in to Git, the DevOps deployment is a two stage process.

1. A build pipeline builds the solution and publishes the build artifacts (ie,...

Nasty! OK, here is another thought. How about pre-processing the file and replacing every occurrence of

n"

(where 0 <= n <= 9)

with n~

Then importing the data, then replacing ~ with "...

Some good input here, but I've run into an issue, that I can't get the team exporting the data to fix.

I'm getting data like this: PartNo,Description,Cost

1234,"Pipe 2"x6" galvanized",1.45

5678,"Frame, Wood,...

I said 'add another THROW', not 'add another THROW 51000, '2. One or more stored procedures had errors, please investigate', 1;'!

Also, surely you want the INSERT to dbo.RunTimeErrors to occur...

• This reply was modified 2 weeks, 2 days ago by  Phil Parkin.

Did you add another THROW in the final CATCH block, like I suggested?

If yes, please post the code.

No, only 1 TV is required. You simply run multiple INSERTS to it in your code.

To make the error appear in the SSIS Output window, you need to add THROW...

Instead of logging your errors in a physical table (whose changes are being rolled back, I assume), log them in a table variable and then insert from the table variable...