Many people are in the database design, or they like to design the database structure in the format of the Word document, and make the creation of the physical database; and the database modeling tool is really small; if you don't ask those not Willing to use the database modeling tool why, I think they will usually give you the following answers:
1. The database structure is not complicated, and it is not necessary to use modeling tools.
2. Modeling tools are more troublesome, unrealistic.
3. Our company has a dedicated database document format, I am afraid modeling tools can't generate a suitable document.
For the above answers, I think it is not established because it causes the misunderstanding of modeling tools.
Take PowerDesign as an example, the answer to the above answer can be respondent.
Some people think that the use of modeling tools must be complex data analysis, in fact, this is a misunderstanding; the database modeling tools certainly have some of this capability, but not important, not necessarily. You can concentrate on the design of the database, just establish each entity and their relationship, this work is completed, the entity's properties are the fields of the table, the relationship between the entity is the table and The relationship between the tables, the character input of this process is no more than the input of Word you use; and when you are as skilled in the modeling tool, this process is less than you use Word Design. The time of the database. More importantly, as long as this step is completed, you can directly generate SQL code for the database, or let the modeling tools and databases connect, so you can change the database structure by changing the entity and the relationship between the entities and them. . And the traditional way of using Word, you must re-tap the field name and type when you build the database, and in order to ensure the database established by this process and the consistency of the database structure you use by Word, you must pay Additional labor. Worse, if you change the database, if you change from SQLServer to Oracle, I am afraid that the effort is more energy. The database modeling tool does not have this shortcoming, which should be independent of the database platform, so you can simply port it to a different database platform.
Moreover, most of the database modeling tool is a graphical interface. This is more favorable and entity relationship. At least a text method is intuitive, concise, now you build a relationship between a primary key. Just use a control, It is possible to do a few more choices.
The database modeling tool also supports powerful data export features, which can generate hypertext or Word documents in full custom format, which can meet the output format you want, and this operation is not complicated, you can say this, at least Data document format, can be exported using PowerDesigner.
There is also the benefits that you can't think of, now there are now many data library modeling tools support code generation functions, you can generate some basic data operation code, and support multiple languages, such as PowerDesigner supports .NET, Java, Pb, Delphi and so on. Language.
Imagine, you only need to pay less energy and time to design the database structure with Word, you can get a cross-platform, consistent, graphical interface, format freedom to take the code generation function, why not don't need it? ?
Oh, the above is a bit of thinking of the XXX project database design, I hope to help everyone :)
