I have package that is importing several flat files to the database.
The package runs successfully when developing in BIDS.
When I deploy the package to the server and attempt to run it I get the following error.
Description: Data conversion failed. The data conversion for column "Year" returned status value 2 and status text "The value could not be converted because of a potential loss of data.".
Now comes the "weird" part. The failure seems to be dependent on where the file resides not the destination.
If I run the package in BIDS with the source file and destination connection both my local laptop then it executes successfully.
If I run the package in BIDS with the source file local and the destination connection pointing to the test database server, then it executes successfully.
I I deploy and execute the job from a SQL Job with both the source files and the destinations being the SQL server where the package resides, then I receive the error.
The source flat file is the same file in both locations.
Any idea why having the file in a different location (not a network/shared location) would cause it to fail?