Hooznext
asked on
SSIS Flat File Destination File Extension Case Issue
Hello all,
I have an SSIS package that formats a flat file for importing into a third party application. The problem I am running into is the file extension of the file destination connection is showing up as upper case and the third party requires lower case. So my SSIS generated file is coming out as "DataFile_CCYYMMDD.POS" and it needs to be "DataFile_CCYYMMDD.pos". All of my variables are showing the file extension as lower case .pos, the file connection manager shows it as lower case, the expression on the connection evaulates to lower case, the script where I concatenate the date into the file name shows lower case extension, but file is written to the hard drive with an upper case extension. I have been unable to find where I can change this. Any help is appreciated.
I have an SSIS package that formats a flat file for importing into a third party application. The problem I am running into is the file extension of the file destination connection is showing up as upper case and the third party requires lower case. So my SSIS generated file is coming out as "DataFile_CCYYMMDD.POS" and it needs to be "DataFile_CCYYMMDD.pos". All of my variables are showing the file extension as lower case .pos, the file connection manager shows it as lower case, the expression on the connection evaulates to lower case, the script where I concatenate the date into the file name shows lower case extension, but file is written to the hard drive with an upper case extension. I have been unable to find where I can change this. Any help is appreciated.
At end of the Package use File system task and rename the file.
ASKER
MrNetic, it is not in production yet, I am running this through Visual Studio. It is ready for final testing as soon as I figure out why all the extension are capital letters.
Patel, I could do this, depending on the day there can be thousands of files created by this job, to have to loop over them and rename them would introduce more overhead, I'd rather have the files named appropriately when they are created. This idea is a last resort for me.
Patel, I could do this, depending on the day there can be thousands of files created by this job, to have to loop over them and rename them would introduce more overhead, I'd rather have the files named appropriately when they are created. This idea is a last resort for me.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Was an issue created by an admin in our database, nothing to do with SSIS.
If you are running this as a job, you should check if someone else has changed the ssis job step, incluing package configurations and datasources.