Each time during conversion, attributes in subtypes get duplicated inside the containing table. Likewise the table fills up with more and more duplicated check constraints.
Step to replicate the problem.
1) Create a logical model with an entity Employee and a subtype InternalEmployee. The inheritance is set up as exclusive. The subtype has one attribute, "Bonus".
2) Next use the Convertor to merge the logical model into a physical model. The first time it works fine, get a table called "Employee" with a column "Bonus".
3) The problem is that each time the Convertor is run from then on, it creates a new column called "Bonus" in the table. It also creates the check constraint needed to enforce the Bonus column as mandatory, even though it already exists in the table.
Conversion from logical to physical model depends on settings defined in logical model, especially settings for inheritances.
To avoid possible problems, convert the updated logical model to a new physical model and then compare the two physical models. Add modified or newly added objects to the existing physical model. In other words, do not update physical model directly from logical model, instead do a conversion first and then compare the two physical models.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center