Topic > Database system integrity

System integrity refers to the correctness and consistency of that particular system. The integrity of the database system refers to the correctness and consistency of that particular data entered into the database. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an original essay Sanity checking is classified into two modes Implicit checking mode Explicit checking mode Implicit checks are those that allow domain, tabular, and referential constraints the same as those applied in the relational model rules. Explicit controls are those that force the application of the administration and management control rules envisaged by the DDBMS. As specified, explicit checks are one of the two key elements (along with views) of certificate approval of relational database architectures. According to Bell and Grisom [BellGris92], ensuring data integrity is rather difficult in a heterogeneous distributed environment compared to a homogeneous one. The main central control entity indicates the level of complexity to manage integrity constraints. High core central control is inversely proportional to the difficulty of managing integrity controls. In a homogeneous distributed environment the central control is very strong because the DBMS schemas of each database site are the same. However, integrity checks are easily satisfied in a homogeneous environment. While on the other hand in a heterogeneous distributed network the DBMS schemas of multiple organizations on some sites are different, so in a heterogeneous environment many problems will arise that threaten the integrity of distributed data. There is a list of 3 problems that arise due to heterogeneous network behavior: Contradiction between local health checks Difficult to define global health checks Contradiction between local and global checks Local health checks are easy to implement in a distributed environment because they are limited to respective organization of the site. On the other hand, global health checks are separate from their respective organizations. It was taken into account as an entire database. It may never be applicable to alter the structure of the entire organization just to configure the deployed environment compliantly. Bell and Grisom explain that local health checks differ relatively in the heterogeneous distributed database. The differences result from the differences in the respective organizations. This inconsistency can lead to problems, particularly with particular composite queries that depend on data residing at multiple sites in the database. The strategy adopted to perform global integrity checks can reduce inconsistency between individual databases. But it is not as simple to implement as simple to say, while alternatively global integrity controls are moved away from individual organizations. Creating a distributed environment by modifying the architectural model of individual site databases is a very impractical way. Please note: this is just an example. Get a custom paper from our expert writers now. Get a Custom Essay Ultimately, it will result in a contradiction between local and global controls. The central control level is linked to the present Inconsistencies. If there is strong global control, global integrity control will take priority. If central control is not strong enough, local health checks will take precedence.