Teach you to use database modeling tools for database modeling

A lot of people in the database design, still prefer to use Word document format to design database structure, then the creation of physical database, and the real use of database modeling tools for database design is very few; If you interrogate people who don't want to use database modeling tools, I think they will usually give you the following answers:

1. The database structure is not complex and there is no need to use modeling tools.

2. Modeling tools to use more cumbersome, unrealistic.

3. Our company has a special database document format, I am afraid the modeling tool can not generate the appropriate documentation.

For the above answer, I do not think it is true because of the misunderstanding of modeling tools.

Take powerdesign, for example, to respond to the above answers.

Some people take for granted that the use of modeling tools requires complex data analysis and so on, which is a misunderstanding; The database modeling tool is of course part of this capability, but not important or even necessary. You can focus on the design of the database, only need to establish each entity and their relationship, this work is completed, when the entity, the entity's property is the table of each field, the relationship between the entity is table and the relationship between the table, the process of character input is never greater than you use Word input quantity And, when you're familiar with modeling tools like Word, the process takes less time than you use Word to design the database. More importantly, as soon as this is done, you can directly generate the SQL code to create the database, or have the modeling tools and databases connected, so that you can change the database structure at any time by changing the entities and their relationships. The traditional way of using Word, you have to create a database, the field name and type to restart again, and in order to ensure that the process to build the database and the original you use Word design database structure consistency, you must pay extra labor. What's worse, if you change the database, for example, from SQL Server to Oracle, I'm afraid it will take more effort. The database modeling tool does not have this shortcoming, it should be independent of the database platform, so you can simply migrate to different database platforms.

Moreover, most of the database modeling tools are graphical interface, which is more advantageous to the establishment of the entity relationship, at least more intuitive than the text, concise, and now you build a relationship between the main foreign key just put a control, and then make a few choices on it.

The database modeling tool also supports powerful data export capabilities, the ability to generate fully customizable hypertext or Word documents that meet the output format you want, and the operation is not complicated, so to speak, at least I have seen the data document format, using PowerDesigner can be exported.

There are more to your surprise, now many database modeling tools support the code generation function, can generate some basic data manipulation code, and support a variety of languages, such as powerdesigner support. NET, Java, Pb, Delphi and other languages.

Imagine that you just have to pay more than using Word to design the database structure less energy and time, you can get cross-platform, good consistency, graphical interface, format free and code generation function.