After our interactive demonstration showing how to create a database from scratch quickly and easily with ER/Studio, we had a terrific post webinar discussion on this topic. I wanted to share with the community the video created as well as some documents that came out of the process.
A link to the webinar VIDEO
A link to the model file we created in real-time as well as a couple of macros used to speed up the process. LINK
Below is the Q&A follow-up:
Q: Do we have concept of reverse engineering the Logical Model from text (say excel file where entity and its attributes are mentioned)?
A: Yes, this can be done through the use of two macros both included in the Data Architect installation:
EXPORT OBJECT DEFINITIONS AND NOTES FROM EXCEL
IMPORT OBJECT DEFINITIONS AND NOTES FROM EXCEL
Q: Is there a way to specify schema in the model(s)?
A: Yes, this can be done in the left-side tree-view pane under the Physical model there is a node called Schema. Simply right click on this and add your schema(s).
Each schema can then be applied to a table by opening the table and selecting it from the Owner drop-down.
Q: I am using 9.7 version which is pretty old and does it have DDL generation by comparing different versions of the models?
A: No, the models must be of the same version for the compare to work.
Please contact your Account Manager to discuss some of the interesting changes that have taken place in the latest version.
Q: Do you recommend source code control on the ER/Studio file?
A: Yes, though these files can reside anywhere, GIT, TFS, etc. those will only show that a file has changed and not what was changed.
We suggest that you check out the documentation for the Professional edition to acquire a repository which will allow you that very specific version control and model management that you would expect from any source control offering.
Q: Is there a way to document this model and export it to .PDF?
A: Yes, go to Tools -> Generate Reports and select the type of report you wish and use your pdf printer driver to save as a pdf.
Q: How can I share domains with my colleagues?
A: A single model can house the main data dictionary and all other modelers can go to File -> Import Data Dictionary to pull that into their own model.
A better solution is through the Professional Edition as this allows you to promote a Data Dictionary to Enterprise level, allowing all other modelers to use that in their model.
This solution also migrates changes from the enterprise data dictionary automatically to the sourcing models giving you as an administrator further reach into the management of all other models.
Q: Do you have in built version control for a model that undergo changes during the project implementation?
A: Version control can be handled in the Professional edition through the use of Named Releases. This enables not just version control but also allows for the documentation process through the entire data definition life cycle.