I reverse engineered a SQL Server 2005 database, and the RE worked flawlessly with one exception.  This block of code is the actual CREATE TRIGGER used to create it in SQL Server (outside of ModelRight):

 CREATE TRIGGER [EDW].[ProductUpdateTrigger]
    ON [EDW].[DIM_PRODUCT]

...

END

 

 This block of code is what ModelRight reversed engineered:

CREATE TRIGGER ProductUpdateTrigger
    ON DIM_PRODUCT

...

END

 

As you can see, the schema is missing.  This causes the database compare / forward engineer to fail.

Can anyone provide guidance?

You need to do two things:

1.  Assign an owner/schema to it.

2. In the Schema Gen Options, under  Miscellaneous you need to check Schema Names,

Hope it helps.

 

---

ModelRight Evangelist

You also need to set the Schema Gen Option/Misc/Quote Names option

---

Scott Reynolds
Senior Technical Support
ModelRight, Inc.

I have manually assigned schemas to all of the triggers, but the DB Compare is still not reverse engineering the schema name.  It now thinks all of the triggers (to which I assigned schemas in MR) are new -- they don't match up to the triggers of the same name in the database (because the RE database triggers don't have schema).

 

This all occurs before I get to the Schema Gen Options window.