Integrity Constraint In Database

Integrity: Database displays the integrity. It means that accurate reflection of its UOD. The process of ensuring integrity is a major feature of modern information systems. The process of designing for integrity is a much neglected aspect of database development. e.g. Extension: Company Modules: Computer Science Department Marketing Department Electronics Department Employees: Rohan Sohan Mohan

Works: Rohan works as Software Developer in Computer Science Department. Sohan

Database should be a repository with no replicated fact. Transaction: The events that cause a change of state of database is characterized in database terms as transaction. A transaction changes a database from one state to another. e.g. A transaction type that might be relevant to the company database system might be enroll Employees in Modules.

Integrity constraints: Database integrity is ensured through integrity constraints. An integrity constraint is a rule, which establishes how a database is to remain an accurate reflection of its UOD. Constraints may be divided into two major types: Static constraints and transition constraints.

Static constraints or “state invariant” is used to check that an incoming transaction will not change a database into an invalid state. A static constraint is restriction states of database.

Transition constraint is a rule that relates given states of database. A transition is a state transformation and can therefore be denoted by a pair of states. A transition constraint is a restriction defined on a

These applications might be used to create form or generate a report. Example: If you are designing an order entry application for users, you could use the application generation component to create a menu system that makes the application easier to use. Typically, IT Professionals and database administrator use this component.

Data Administration: The administrator component also used by IT professionals and database administrator, is used for tasks such as backup and recovery, security, and change mgmt. In addition, this component is used to determine who has permission to perform certain functions, often summarized as Create, Read, Update, Delete(CRUD).

Database design management is handled by the database administrator (DBA), although with complex databases, this task is sometimes handled by an entire department. The DBA’s responsibilities include the following:

1. Designing and setting up a database.

2. Establishing security measures to determine user’s access rights.

3. Developing recovery procedures in case data is lost or