loading data

[VaughanDA]

Okay. There has to be an easier way. I am convinced I am making this
too hard.

If I go to MS/Excel and open the CSV file, I get no errors.

If I use MS/Access to open a CSV file, I am asked a few questions but,
in general, I see the data with no errors.

Why then am I overwhelmed with truncation errors (and others) when
attempting to use SSIS or BULK INSERT?

How do you load YOUR data? What do you use? What works? What are
the best practices? This seems silly but I am being frustrated over a
"simple" data load. Your comments are welcome.

Many thanks.

David Andrew Vaughan

[Hong Zhang]

David,

In SSIS, did you specify the column length or data type for your destination table? SSIS has some default column type/width which may cause the truncation of your data.

Thanks,
Hong

--

You received this message because you are subscribed to the Google Groups "AtlantaMDF" group.
To post to this group, send email to atlan...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/atlantamdf?hl=.

[Ramy Mahrous]

What's the error you get when you try that?? or you just need a walkthrough to load data
http://ramymahrous.wordpress.com/2009/11/04/ssis-insert-bulk-of-data-into-remote-table-with-trigger/

--
Thank you,
Ramy Mahrous
BI Developer | LINK Development
Business Intelligence Blog | http://ramymahrous.wordpress.com/
Technical blog | http://fci-h.blogspot.com/

[Debu]

Let me understand the issue. What exactly are you trying to do ---
extract data from a table as csv?
If you are extracting data as csv and the file does not exist then you
will not receive any truncation errors.
Please explain

[Donald Wert]

The truncation messages indicates that at least some of the data in the CSV file is too long for columns in the target table.  Does the target table already exist or are you creating it on the fly?  Are you getting messages on all columns or specific ones?  If you can narrow it down to one or two specific columns it would be useful to open the CSV file in Excel and use the len() function against the offending column(s) to see what lengths you get.  If you are creating the table on the fly there's a chance that when SSIS samples the data it's not seeing records with the overly-long values so it assigns lengths that are too short.  Same with numbers.  If it sees integers in the first few rows but there are decimal values on down, you will get errors.

 

On Tue, Nov 10, 2009 at 1:45 PM, VaughanDA <vaug...@gmail.com> wrote: