Source data size should be equal or less than destination data size, otherwise, it will have truncation warning.
To be continued.
A place to share my BI experience with the world... also make sure I won't forget what I have achieved in this fascinating area...
Source data size should be equal or less than destination data size, otherwise, it will have truncation warning.
To be continued.
I am assigned to a task and this task sounds quite easy: load data from a csv file into an access 2003 table. I used SSIS2008 to complete this job and it appears the traditional unicode and nonunicode conversion errors was blocking the development. After investigation, I realized that all text columns in access are unicode-enabled default. Since all incoming columns are converted to DT_STR, that caused the conversion error. I am still trying to find a way to solve this issue, will keep updated once it’s found.
I am working on a small ETL task trying to extracting data from a workbook. Some cells do not seem to contain any values but ISBLANK() shows false.
After some research, I found out if you put =”” into the cell, it will not display anything but it’s not blank. This could be very misleading when in extracting data from workbooks. The best way is to save the excel file as a csv file and launch the notepad apps to replace “ ,” with “,” to remove any spaces in between commas because the space in the cell was shown as a space in csv.