November 16, 2012 at 6:01 am
I have several .csv files and i'm trying to insert them into a database table.
all my files are saved from an excel spreadsheet - saved as .csv.
I'm trying to import these into a table varchar(50).
All my data in the single field being inserted into the table are only 7 characters long (uk postcodes) but changed to varchar 50 as it was giving me error about the field not being long enough.
Here are 14 screenshots of my table, my data and all my settings:
http://www.sypensions.org.uk/test/test.html
thanks,
mark.
November 16, 2012 at 6:04 am
can you copy out all of the output window and paste it in a txt file and attach it, the screen shot strips out the important bits at the end of the lines.
November 19, 2012 at 5:22 am
November 19, 2012 at 5:26 am
Thats a warning, it wont cause the package to fail.
The screenshots detail Errors, one of which was inserting NULL into a column which didnt accept NULLs as well as other errors
November 19, 2012 at 5:51 am
I have made some recent changes since the first screenshot.
Such as making sure there are no spaces in the excel csv files, that they are all equal length and
making sure the ole db destination datatype is DT_STR etc.
and even though it no longer says error and now says 'warning & information messages'....
it does not write anything to my database table at all.
November 19, 2012 at 5:59 am
There is no data in the file for it to import.
The error states it reached to end of the file before importing anything and to check the field and row terminators and ensure your not skipping any rows that you dont need to skip.
November 19, 2012 at 6:23 am
thanks for the replies anthony.
I think i tried too many things at once and got a bit lost.
it's now importing ok !
for the txt file which shows the warning message....
I had moved all my csv files except one - which i had tried to amend to uses commas inside the file rather than columns.
I then put the csv files back to normal (with columns). and took note of the NULL message.
I changed the IDNo field to accept NULLs and it then it started working.
However, as for the IDNo field - i don't want to import this and didn't think I was importing it (because under mappings i only have column 0 mapped to 1 field called postcode - so didnt think this field should matter, but maybe it needs to be NULL if data is not being imported into it - due to data being iserted into the adjacent column?)
November 19, 2012 at 6:30 am
I am guessing the problem is that you haven't set IDNo as an identity to autopopulate with an ID number. The error is being thrown by the SQL server saying you cant insert a row as you havnt told me what value to put in the IDNo column as it cant take nulls, as like you say you only have the PostCode column mapped.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply