Arithmetic overflow into SQl server bulk loader

JPalatianos · Post by **JPalatianos** » Fri Mar 25, 2011 7:31 pm

Hi,
A developer just ran into a problem when he is running his data into a target MS SQL Server Load stage...he gets the warning:
cfsstg_finance_database_stage_2_jptest..Cfsstg_finance_database_stage_2_ins.IDENT2: Arithmetic overflow

When he changes the target from the MS SQL Server Load to an ODBC stage with every thing else unchanged he runs clean. I looked at the job and am not sure where IDENT2 is coming from.

Any ideas?

Thanks - - John

chulett · Post by **chulett** » Fri Mar 25, 2011 8:15 pm

Those are the names given to 'invisible' transformers the compiler adds to your job between passive stages when you don't put them in yourself. That was the second one in that job.

JPalatianos · Post by **JPalatianos** » Sat Mar 26, 2011 6:23 am

Thanks! Now for the question:
Why when changing the target from the MS SQL Server Load to an ODBC stage with every thing else unchanged he runs clean. Why would the arithmetic overflow just show for the bulk loader?

chulett · Post by **chulett** » Sat Mar 26, 2011 7:29 am

Now that one I can't answer. Problems in Server jobs are always reported by the active stage, hence the error from the transformer when the bulk loader went astray. You'd probably need to involve your official support provider if you really wanted to track that one down.

ray.wurlod · Post by **ray.wurlod** » Sat Mar 26, 2011 4:44 pm

Perhaps the SQL Server loader stage checks the range of unsigned integers as if they were signed, and the ODBC stage doesn't. This is one for your official support provider - that was just a guess on my part. Of course, your job design could ensure that out of range values never reach the stage in the first place.