Problem in Loading data through SQL Server Bulk Copy via API for nvarchar type

[akbara]

Hi,

I'm loading data into a SQL Server 2005 database and having problems with nvarchar columns when using the delivery method of 'SQL Server Bulk Copy via API'. The data has a carriage return appended to each nvarchar column. So the length of all the nvarchar columns is incorrect aswell as the data of course.

There is no problem when I use either the "Relational Table" or "Microsoft SQL Server BCP Command" delivery modules.

In terms of speed (based on 100,000 records) I get the following results

14 seconds to load           "SQL Server Bulk Copy via API"
1 minute and 11 seconds   "Relational Table"
1 minute and 11 seconds   "Microsoft SQL Server BCP Command" delivery module.

So you can see why I would like to use the "SQL Server Bulk Copy via API" delivery module

Can anyone please tell me why this is happening on the "SQL Server Bulk Copy via API"  delivery module?

[akbara]

No luck so far so I've created a support call with IBM. Hopefully some of the Data Manager techy guys will have a look and advise about the problem.

[akbara]

This has been identified as a bug and an issue call has been raised.