I have seen a problem in the past which may be related. In my case, the version of .NET being used by SSDT appeared to be a later version than...

Your variable @source is not being set, hence the NULLs.

Package properties don't affect the bitness when set up as an Agent job.

Instead, to run a package in 32-bit mode from a 64-bit version of SQL Server Agent, select Use...

I assume you are familiar with the REPLACE function, with which one can easily change the _X0020_ back to a space?

If you are asking about how to avoid the issue...

Do you believe this to be a detailed and thorough response to...

The biggest benefit I can think of is that this method provides total control over how changes get deployed, rather than relying on SSDT's schema-differencing and updating tech, which is...

Can you explain the logic behind this requirement, please?

I cannot see any questions in your post. What, specifically, do you need help with?

Can you provide some sample code which we can cut & paste into SSMS?

Microsoft Excel,...

Easiest way is probably to use Brent Ozar's PasteThePlan. Instructions here. Once you've done that, post the link here.

Still can't get pass this error:

Type conversion in expression (CONVERT(int,[d2].[attValue],0)) may affect "CardinalityEstimate" in query plan choice, The query memory grant detected "ExcessiveGrant", which may impact the reliability. Grant...

I second everything Brian Gale has posted here. Excellent advice.

Another possibility is pushing the contents of the table to a text file on the remote server, zipping that, copy to local server, unzip and import.

As implied in the previous...