Tried importing it to Access and then Access to SQL? Access is a lot more forgiving and you will then have fixed width fields to feed to SQL.
Thanks, Brian Desmond [email protected] c - 312.731.3132 From: Benjamin Zachary - Lists [mailto:[email protected]] Sent: Wednesday, January 28, 2009 9:15 AM To: NT System Admin Issues Subject: sql importing Just checking if any decent SQL guys out here, I have a bunch of data Ive been asked to import into a new table in SQL 2008, easy enough except the data is pretty messy. I run the import wizard and I keep getting errors about truncation and aborting. I tried to reset the fields to unlimited length of type string or text and still happens. I don't mind truncating the data and went through some advanced options to say ignore truncation but that doesn't seem to work. I brought the data (csv) into excel and saved the xls and then tried to import there but after 6 hours its still not done, so it was probably hung up somewhere. Besides going through 290,000 records of 50 fields by hand is there a decent way to get around that? Im sure for example that my State field shouldn't be 180 chars long on record 10,700 (an error I received) so truncating it to under 50 should be Ok, if I can get around the error. Thanks ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
