[Er/studio] Merging different versions of the database structure

Data | database | database structure
Difficulty coefficient: 0
This article aims to:
Introduction to Er/studio Database modeling software, feel better than rose and Visio database modeling and easy to use
No Erwin garbled problem, PowerDesigner has been no use, hehe, heard has not seen:

A system developed by the company, because it is provided to the customer code, so the customer carried out two times development.
At the same time for the expansion of the product, our company itself has been further development.
Later, as needed, the customer asked us to upgrade the system with our current program based on their existing programs.

Both sides of the code are not significantly modified, using VSS can be compared to confirm the difference.
But the customer for the convenience of statistics and inquiries, added a lot of tables and fields, but also our side of the database has made some changes
The integration of the database has become a problem, hehe, although there are many ways, such as: Into the SQL statements, contrast and so on
But the workload is not small. Later use Er/studio solve this problem, more relaxed, it seems that there is a hand tool is good.

1: First, reverse two databases into two modeling files model1.dm1 and MODEL2.DM1
2: Open MODEL1.DM1, and then follow the diagram step-by-step, very easy.












Before clicking on "Finish" to do the actual processing, suggest that Mr.



Choose HTML format, the back will look more convenient



The key is to delete a table in the target table that does not have a source table.


If you want to keep it, take a few steps back and remove the hooks from these tables.

Select and then advance to the final interface click "Finish" to operate.

Note: If too many database tables may cause software exceptions