Data Flow problem - incomplete varchar field

#41

As a further bit of update information. I am beginning to believe that
the problem I am having is due to the subject field on the ODBC database
having nulls embedded in the field. So the DT_WSTR data type is reading
the field up to the null and stopping.
Is there some other data type or some othe way to approach reading this
column of data even with the embedded nulls in the field?

Dennis

"Irvine, Dennis" <dennis.irvine (AT) plumasnt (DOT) com> wrote

Quote:

I am working on migrating a database for SQL 2000 on a Windows 2000 server,
over to SQL 2005 on a Windows 2003 server

A large amount of the data in the database is refreshed everyday by
pulling data from an external ODBC source.

On the SQL 2000 installation I used a DTS package to import the data from
the ODBC source and it works fine.

On the SQL 2005 installation I completely re-wrote the DTS package into a
SSIS package.

My problem is that there is a text field that only imports a portion of
the field from the ODBC over to the SQL 2005 database.
The field is 400 chars long, but for some reason, only 200 chars or less,
will come over to the new SQL 2005 field.

I am using an ADO.net ODBC connection manager and a Datareader object to
get the data from the ODBC source.

Now on the old database I can get the whole 400 chars in this text field
to come over. But in the new database it only reads part of it.

I am thinking it has something to do with "Unicode" and the SQL 2005
package reading the field as a DT_WSTR data type, even though the source
field is not that type.

Anyone have an ideas?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Data Flow problem - incomplete varchar field

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

Re: Data Flow problem - incomplete varchar field - 10-15-2008 , 09:39 PM