Automatic Increase of Database Field Sizes.....BAD!!

Hi

We have numerous transformations that we utilise between different environments which may take data from a source where the field length in the source is larger than the target database.

I know PDI has the ability to tell me where table changes are required and provide the sql to run this.
It's very useful for telling me this information but extremely dangerous if run in our environments due to the way the overlaying software handles it's field lengths.

It seems that (not sure if other databases too) when migrating to SQL Server it is running this SQL regardless.
It used to give me an error stating that data truncation would occur.

Is this something that can be turned off or something other people have seen?
I find it difficult to believe that this is the default behaviour now, to auto extend fields where data truncation would occur.

Just to be clear, we have NOT accidentally run this SQL. In this particular environment it has never even been viewed.

Any thoughts? Is this a JIRA? Or am I doing something wrong?

Bill