Best Practice for Model Files
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?
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?