J
Jesper Jensen
Hi.
I'm reverse engineering a DB design for SQL server. In
this design, I've used UDTs with defaults attached to
them, e.g. MyInt (Int), default value: [dbo].
[MyIntDefault].
When I reverse engineer this, I get errors in my model:
Table.Field: The default value is incompatible with the
data type or is too long.
Visio actually reverse engineers the DDL for the default,
e.g. "create default [MyIntDefault] As 0", and calls it a
literal type - clearly wrong.
Is there anyway I can modify the reverse engineering
process to handle this case? Or is this just a short
coming of the reverse engineering?
Needless to say, that I will not use round-trip
engineering, if I manually have to change the defaults for
all my fields every time around!, and then Visio turns
into a doc tool, instead of a modeling tool
.
Rgds
Jesper Jensen
I'm reverse engineering a DB design for SQL server. In
this design, I've used UDTs with defaults attached to
them, e.g. MyInt (Int), default value: [dbo].
[MyIntDefault].
When I reverse engineer this, I get errors in my model:
Table.Field: The default value is incompatible with the
data type or is too long.
Visio actually reverse engineers the DDL for the default,
e.g. "create default [MyIntDefault] As 0", and calls it a
literal type - clearly wrong.
Is there anyway I can modify the reverse engineering
process to handle this case? Or is this just a short
coming of the reverse engineering?
Needless to say, that I will not use round-trip
engineering, if I manually have to change the defaults for
all my fields every time around!, and then Visio turns
into a doc tool, instead of a modeling tool
.Rgds
Jesper Jensen