Yes, it's SSIS.

The source system is hadoop. We thought about the possibility of time zone issues but we've tested in two different time zones and still got the result of...

I discovered rolling back SQL updates doesn't rollback updates to Microsoft ODBC Driver 13 for SQL Server. The easy way would be to rollback SQL to 13.0.6450.1, uninstall the ODBC...

We don't use that but our ODBC Driver 13 version matches what you have. The date which it was installed/updated coincides with the date the latest SQL patch was installed....

I see Microsoft ODBC Driver 18 for SQL Server updated on our end between 2016 SP3 GDR 13.0.6450.1 and 2016 SP3 GDR 13.0.6455.2. These windows updates were installed during the...

While we don't use that, I do find it very interesting that we are also running the same version. Several weeks ago I tried rolling it back but the issue...

It does use linked servers but I ruled that out since we specify the security context being used. Meaning any reference to the linked server uses the same SQL authenticated...

All other procs are fine. That's what is making this extra difficult. The proc completes locally within a few minutes so it's not an overly long-running proc too.

The code provided was just for explanation purposes. The real one I was using accounted for about ten different variations although I don't think that is still the best way...

I get the reasoning for taking the first 50 characters before the table name but I'm not sure it would accomplish what I want. If I use a charindex in...

I also put something like that together where it would look like this

where ([definition] like '%INTO [tableName]%' or ([definition] like '%update [tableName]%')

That got me the closest I've...

I did come across Pinal Dave's solution but that is different than what I'm trying to do. The solution he lists returns any object dependent on the table whereas I'm...

That is exactly what is happening from a process flow standpoint. However, it succeeds with Windows authenticated accounts so that's why it isn't lining up in my mind.

To add more confusion, it will work if I make AppUser a sysadmin on Server A. However, this isn't an option to keep.

I've dealt a little bit with the double hop issue but this seems to be a little different in the sense it only impacts SQL authenticated users.

The app is passing...

Unfortunately I need to deploy to the file system for this particular project. I think switching from project deployment to package deployment was the missing link I needed. I started...