Transaction Processing System - Databases and Files

Databases and Files

The storage and retrieval of data must be accurate as it is used many times throughout the day. A database is a collection of data neatly organized, which stores the accounting and operational records in the database. Databases are always protective of their delicate data, so they usually have a restricted view of certain data. Databases are designed using hierarchical, network or relational structures; each structure is effective in its own sense.

• Hierarchical structure: organizes data in a series of levels, hence why it is called hierarchical. Its top to bottom like structure consists of nodes and branches; each child node has branches and is only linked to one higher level parent node.
• Network structure: Similar to hierarchical, network structures also organizes data using nodes and branches. But, unlike hierarchical, each child node can be linked to multiple, higher parent nodes.
• Relational structure: Unlike network and hierarchical, a relational database organizes its data in a series of related tables. This gives flexibility as relationships between the tables are built.

The following features are included in real time transaction processing systems:

• Good data placement: The database should be designed to access patterns of data from many simultaneous users.
• Short transactions: Short transactions enables quick processing. This avoids concurrency and paces the systems.
• Real-time backup: Backup should be scheduled between low times of activity to prevent lag of the server.
• High normalization: This lowers redundant information to increase the speed and improve concurrency, this also improves backups.
• Archiving of historical data: Uncommonly used data are moved into other databases or backed up tables. This keeps tables small and also improves backup times.
• Good hardware configuration: Hardware must be able to handle many users and provide quick response times.