Reputation: 138027
I have an SSIS package that is using a Lookup:
It all works well from my machine, naturally.
I can install the package on production, but when running it it quickly fails on validation of the Lookup:
input column [ColumnName] (238) and reference column named [ColumnName] have incompatible data types
This is clearly a lie - they have the same types. It looks like this is a known problem of the Lookup component:
In both cases, some people suggested running the package in 32 bits solved their problem. However, my package fails connection to the server when running in 32 bits...
What am I missing? Should I install additional x86 providers?
Is there a good way of fixing the Lookup?
Upvotes: 1
Views: 1139
Reputation: 67
I know this is an old post, but if anyone stumbles here, here's my solution.
I was getting this same answer, and in the query for the lkp, I explicitely converted the problem data type using a CAST statement. I too was having no problems in debug, but was getting the error when it was deployed and run on SSMS. This fixed it for me.
Upvotes: 1
Reputation: 138027
As a workaround, I was able to open the Microsoft Visual Studio 2008 Shell on the production server, and run the package through there. Since this is a one-time migration job, I don't really mind.
Upvotes: 0