Hi all,
When I try to import a fixed field Unix textfile into a SQL-server table i get some strange result. I'm using LF as a row delmiter.
This is what I get when I look at the table after the import:
Field1 Field2
30180000014 500
3018
30180081222 015
As you can see the second record is sort of 'cut off'.
If I do the same import to a Access table i get the correct answer:
Field1 Field2
30180000014 500
30180000015 500
30180081222 015
If I study the textfile in a Hex-editor I can see that (simpified):
30180000014 500{LF}30180000014 500{LF}3018
0000015 500{LF}30180081222 015{LF}
Is there a bug in SQL 'DTS import textfile'
/Kent J.
When I try to import a fixed field Unix textfile into a SQL-server table i get some strange result. I'm using LF as a row delmiter.
This is what I get when I look at the table after the import:
Field1 Field2
30180000014 500
3018
30180081222 015
As you can see the second record is sort of 'cut off'.
If I do the same import to a Access table i get the correct answer:
Field1 Field2
30180000014 500
30180000015 500
30180081222 015
If I study the textfile in a Hex-editor I can see that (simpified):
30180000014 500{LF}30180000014 500{LF}3018
0000015 500{LF}30180081222 015{LF}
Is there a bug in SQL 'DTS import textfile'
/Kent J.