BrianFord
asked on
SSIS Flat file Source format
I'm using an SSIS job to import data from a flat-file (.txt) to SQL Server
The problem I'm having is that the author of the source file sometimes saves it as Unicode and sometimes as 'non-unicode' so the import either works or 'seems' to work but does not actually import any rows.
Is there a way in SSIS to test what format the flat file is (unicode or non-unicode) before attempting to import, based on that I can branch to alternative import steps.
The problem I'm having is that the author of the source file sometimes saves it as Unicode and sometimes as 'non-unicode' so the import either works or 'seems' to work but does not actually import any rows.
Is there a way in SSIS to test what format the flat file is (unicode or non-unicode) before attempting to import, based on that I can branch to alternative import steps.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Question abandoned
Provided necessary suggestion.
Closing by accepting above suggestions.
Provided necessary suggestion.
Closing by accepting above suggestions.
ASKER
That's what I thought but it doesn't appear to be the case, it simply thinks there are no records in the file, I'll double check the data-types and try again though, perhaps I missed a column
Pawan,
How would you use a script task to do this?