Precision & scale not specified in migration SQL for UDDT to system type

Brian Donahue

Hi Lance,

Thanks for pointing this out. This will definitely get fixed in the next
release.

Sincerely,

Brian Donahue

Technical Support Engineer

Red Gate Software Ltd.

+44 870 1600 037

mailto:brian.donahue@red-gate.com


"Lance Powell" <lpowell@tribute.com> wrote in message
news:QrhKxGo4CHA.1180@server53...
> It appears that there is a glitch in the generated migration SQL when a
> user-defined numeric data type is migrated to a system-supplied numeric
data
> type.
>
> For example, I have a UDDT "mytype" that is defined as numeric(19,4) and
> change a "mytype" column to numeric(19,5).
>
> The migration SQL creates the temporary table column definition correctly
> with numeric(19,5), but the insert statement attempts to cast without
> including precision and scale--CAST ([column_name] AS numeric).
>
> It seems the script should not include the cast and rely on implicit
> conversion--as it does when migrating from one system numeric data type to
> another--or include the complete data type in the cast--CAST
([column_name]
> AS numeric(precision, scale)).
>
> Thank you.
>
> Lance Powell
>
>
>
>