Imvise If we want to transfer a set of old database systems to a new database system, the light is a great challenge for the data structure in the old database system, especially when we must use other DBMS platforms. Early database is more difficult.
The tools provided by Visio make the program more smooth, which uses a powerful "reverse engineering guide" to remove the full database list, including triggers, functions, stock programs, query clauses, and other platforms. In addition, we can easily modify the database design to meet new needs, or establish charts and reports and share results with project team.
1 Supported database
To have maximum elasticity, Visio supports considerable multi-database, including owner's database (such as IBM, Informix, Microsoft, Oracle, and Sybase), desktop database (such as Microsoft Access, and Corel Paradox).
2 Database design based on business rules
If information professionals and general users speak common language, the demand for database design is easier to achieve. With Visio, we can use language to describe business rules for general users and developers, do not have to worry about achieving problems.
3 database engineering reengine
When we plan to plan the database for today's IT project (such as e-commerce or customer management system), we need to be existing DBMS, but don't be hindered by their restrictions, and Visio has the database project we need. power.
4 Collaborative Homework in Working Group
Large database design projects can easily disperse to developer team members, using Visio generated sub-models, each developer can handle a sub-segment on the database, while the centralized project file can merge the source model to display complete Status, the change of the information sheet and the field name is encompassed from the source model, and then the database is generated, the team work is easier than ever.
Then, we will come together to "reverse engineering" how to use.
1 Open Microsoft Visio Professional. The Select Draw Type dialog box appears, select "Database" | "Database Model Map" in the category. If you have already opened Visio, select File | "New" | "Select Draw Type" | "Database Model Map" in the menu |
2 Next, we will find more "Database" menu in the menu, select "Database" | "Reverse Engineering".
3 The Reverse Engineering Wizard dialog is open.
4 In this dialog, we can select its data source and select the appropriate driver.
6 Next, the Connection Data Source dialog box appears, because the database established by the author does not set the administrator and password, therefore directly click OK.
5
Please select "Data Source" "
Microsoft Access Database
", Click" Next ".
7 Next, we have to copy the "Sales.mdb" file in the disc parad to the hard disk first, and remove the read-only properties. However, select the file to "Sales.mdb" in "Select Database", and then click OK.
8 Next, the system will ask us to perform the object type of reverse engineering, in general, we do not need to change, click "Next"!
9 Next, which tables are selected or query data to import into the Visio environment, where there is a "T" table; there is a "V" as a query. Here we choose a total selection and click Next.
10 Next, we can set the shape of the anti-project project to add the shape of the anti-engineering project to the current page or later added, here we do not change, click "Next".
11 After setting, click "Finish", so simple steps can be converted to Visio!
5 View and edit database module
We can also add, delete, and modify the action on the module, delete, and modify the table, field, association, etc. In addition, in the view window, you can change for the state of the database module that is open. Next, we will practice how to view the database fields after the reverse engineering will be viewed and edited.
1 Select the "Customer Data" database placed in the page and select "Database Properties" after right-click.
6 View database properties
2 The "Database Properties" window will appear.
3 By this window you can understand the related properties of this database, including: field name, data type, whether there is a primary key, which data domain name is for the primary key.
