Transformation Error SQL Server Field value too long

Hi

Noticed that we were not being alerted to 'failed' transformation when some values being written were too long for the table defined length.

I would have expected the transformation to error out but in this case the error is swallowed and until we did some reconciliations, we were unaware the data was missing.

Am I missing something that should be enabled/disabled?

We will investigate and get back to you

I had a look.

Rejected Records = Rejected by the validator or by our own internal validations like attempting to load the string into a numeric field
Writer errors = Server errors for example missing foreign keys
Global errors, lead to transformation errors: wrong table name or error on abort.

You can address the issue by checking <Transformation Rejected N> variable or
By adding validator objects to check the field's lengths (Set abort on the error)

Thanks Peter.

Appreciate the insight. I guess for me the issue is that this type of database driven response error is being noticed at some level due to the "Error" indictor. But not being noticed by the writer as abortable.

Also, if you notice the log indicates that there were no record errors detected or rejected. Hence, I am assuming that the <Transformation Rejected N> will be zero and therefore not raise any issue downstream.

Yes, we could put a validator in to check length, but this would potentially lead to a maintenance issue should the schema change.

I was wondering if you would consider some type of additional checkbox on the writer. Similar to Abort if Zero Records written.
Perhaps "Abort on Database Schema Error" ... Something like that.

cheers

FYI when I run the test
<Transformation Rejected N> was more than zero

Hi.

I found that in our case (v 6.3.11.6) that the enablement of the "Fail on Zero Writes" and/or "Fail On Abort" Transformation Action checkboxes does cause the transformation to "Fail" when there are underlying row level issues. However, it can provide misleading results and the "Transformation" variables don't appear to be populated correctly.\

If I have them enabled and the transformation ends up just doing Updates and not creates then it seems that it considers this to be "Zero Writes" and thus causes the Transformation to be flagged as "Failed". The records are added and updated as expected.

If I untick these boxes and there are only Updates, then it performs the add/update as expected but ends successfully.

regards