SQL Server Bulk Loader Issue

[pavan.nadiger]

Hello All,

We are facing a very peculiar issue on our production environment when we use the SQLSvr Bulk loader.
We recently added a new column to an existing table and made relevant changes in our server job. An entry for the new column was made in all the relevant stages. There are around 200,000 records which were loaded.
The jobs worked perfectly alright with no records being dropped, however the new column was only loaded with null values though there is data available in the source table and we can see the same, when you use the View Data option in the Source ODBC stage as well.
Has a similar kind of issue been faced earlier by any?
Your inputs and pointers very much welcome.

[chulett]

An entry for the new column was made in all the relevant stages.

Well... the behaviour suggests that this isn't true. I'd suggest you triple-check your job. And this seems like one of those times when getting another pair of eyes to help would be prudent.

[pavan.nadiger]

Hi Craig,

We have actually checked the jobs thoroughly and have found no anomalies. We replaced the SQL Bulk Loader Stage with an ODBC Stage and the job loaded the data in a perfect fashion.

Therefore was considering whether there is any specific issue with the SQL Bulk loader stage?

Thanks and Regards,
Pavan Nadiger

[chulett]

None that *I* am aware of, but that doesn't mean much as we don't use SQL Server.

Best to put that question to your official Support provider I would think, see what insight (or patch) they might have.

[klsrao]

Have you compiled all jobs after moving to production? Try once agiain compiling. Checkup for any triggers on table. checkup all the transformers and routines / Transforms, Containers. Check for any scripts that run after job. check for any stored procedures. It is certain that unless we make some mistake, it doesnt happen.

Lakshmi Srinivas