Database design of Enterprise Management system __ Database

Casually say:

1, I think it is best not to use a system on a database, the business application and system database separation, such as exception handling, the program error log records are built in a separate database. Ease of management to make the structure clear, while controlling the volume of a single database to improve performance. Backup is also more convenient.

2, now do storage space is already a small problem, so the design can consider the appropriate "space for time", that is, the use of storage of some redundant data to improve the system's access to data performance. Now do enterprises are very speaking efficiency more attention to the system response speed.

3, the database table name, field name must be standardized. That is, the implementation of the database design must have a documented design specifications, do not engage in verbal agreement. Recommended use as far as possible to express a certain meaning, short English name.

4, considering the Enterprise group, and the Rise of ASP, the design of the database to consider the system reuse, that is, a system may be used for several units, but also on a server. Consider the connection from the database to make it flexible. By selecting a different database to support the "branch" run alone.