Best Practice for Model Files

0

We are migrating to ER/Studio from ERwin.  We have a large enterprise model in a single model file that we check in/out as we make changes to it.  It has multiple subject areas.  What is a best practice in ER/Studio for this?  Should we have one large file, or separate smaller model files connected as one model?

Responses (3)
  • Accepted Answer

    Tuesday, June 13 2017, 02:36 PM - #Permalink
    0

    In the future, please submit ER/Studio forum questions to:

    http://community.idera.com/database-tools/databasedevelopment/database-administration/data-modeling--architecture/f

    The reply is currently minimized Show
  • Accepted Answer

    Monday, May 01 2017, 07:21 PM - #Permalink
    0

    Anil, thanks for the response.   Actually, my question was after migration.   When we are going to use the Repository to check in/out models, is it a better practice to have all of our models in a large file, or separated into smaller model files and map them?   We are new to ER/Studio and heard that we shouldn't have one large model file.  Is this correct?

    Thanks, Kirk

    The reply is currently minimized Show
  • Accepted Answer

    Thursday, April 20 2017, 01:45 PM - #Permalink
    0

    The best way is to use our Metawizard and use files one by one.

    We have a video to help out.

     

    Migrate ERwin Data Models to ER/Studio Data Architect - YouTube

    Thanks

    Anil

     

    The reply is currently minimized Show
Your Reply

Please login to post a reply