Distributed Database Design Case Study

Tags: My Hobby Essay 200 WordsDissertation Aire ComposeA Model Of Christian Charity By John Winthrop EssayMaster Thesis On Work StressAnalysis Essay Of ArticleProblem Statement In Research Paper

The table of “ Office” is similar to the table of “ Customers” and “ Salesman” but it contains only the data of company’s sales departments.

Information about items is inserted into the table of “ Parts”. The table of “ Invoices” is connected with the table of “ Customer” (CNO), the table of “ Details” (ONO), and the table of “ Salesman” (SALESMAN) because invoices must contain the customer and sales office, and the item’s name.

The difference between the two databases lies in parent and child nodes – child nodes can have several parent nodes in the network database.

The relational database has different tables, each of which consists of rows and columns for data elements.

These connections between tables increase the amount of hard disk space required for data maintenance and changes made in one table affect other tables automatically.

Table 1 The Structure of Classical Relational Database “ Eeva” software is constructed to work in the individual, company, and distributed databases.

There are three most common types of DBMS: hierarchical, network and relational.

Fields and records of the hierarchical database are structured in nodes. Each entry has one parent node, which may have several child nodes.

Every change in the accountancy law is also taken into account in the previous and present versions of “ Eeva”.

The major changes concern the calculation of remuneration.

SHOW COMMENTS

Comments Distributed Database Design Case Study

The Latest from mediashkola-plus.ru ©