I'm reading a CSV file that is ftp'd to our server every night. I'm using a microsoft text driver to open the file and read it directly in my Stored Procedure. It suddenly seems to be barfing on any date that is like this:
The error is: Conversion failed when converting datetime from character string.
I've tried casting, converting. and that in itself throws an error also. it just does not like the date like this
K, so here are my questions.
1) does this have something to do with the text driver?
2) do i need the person generating the file for me to strip out the time element on his side because SQL Server can't handle milliseconds to that degree
3) if this is the text driver, is there a better way to read the data. some other kind of driver?
Now, i can't remember ever see milliseconds that long before but, hey, i guess in different DB systems that is possible.