How can I set the Date Format for dates in the Excel Destination?
Scenario:
You have a package with an OLEDB Source and an Excel + Destination. In the source table you have a field that is timestamp [DT_DBTIMESTAMP] column which is getting converted incorrectly to a number like 43951.5869164352 when loaded to excel. Attempts to convert the column value in the SQL query as well as using a data conversion or derived column in the SSIS data flow do not convert it to the desired format. (Example: YYYY/MM/DD HH:MM)
Solution:
Go to the page http://www.cozyroc.com/ssis/excel-connection.Scroll down to find the parameter "Date Format".You can use this parameter to specify the date format for the Excel File.
Book a Presales Call
Related Articles
Why does my Excel Destination not overwrite the data correctly?
Problem: When using the Excel Destination to Overwrite data, sometimes rows are written, but the existing data is not overwritten correctly. Solution: The property named "RetainSameConnection" on the Excel Connection needs to be set to "False". This ...How can I set the Date Format for dates in the Excel Destination?
Scenario: You have a package with an OLEDB Source and an Excel + Destination. In the source table you have a field that is timestamp [DT_DBTIMESTAMP] column which is getting converted incorrectly to a number like 43951.5869164352 when loaded to ...How can I set the Date Format for dates in the Excel Destination?
Scenario: You have a package with an OLEDB Source and an Excel + Destination. In the source table you have a field that is timestamp [DT_DBTIMESTAMP] column which is getting converted incorrectly to a number like 43951.5869164352 when loaded to ...How can I set the Date Format for dates in the Excel Destination?
Scenario: You have a package with an OLEDB Source and an Excel + Destination. In the source table you have a field that is timestamp [DT_DBTIMESTAMP] column which is getting converted incorrectly to a number like 43951.5869164352 when loaded to ...How can I set the Date Format for dates in the Excel Destination?
Scenario: You have a package with an OLEDB Source and an Excel + Destination. In the source table you have a field that is timestamp [DT_DBTIMESTAMP] column which is getting converted incorrectly to a number like 43951.5869164352 when loaded to ...