In database systems, a consistenttransaction is one that does not violate any integrity contraints during its execution. If a transaction leaves the database in an illegal state, it is aborted and a error is reported.
Logical consistency, on the other hand, is managed both by the database manager, through mechanisms such as validation rules, triggers, integrity constraints, etc., and by the actions of the application.
Because database changes are buffered in memory and are written back to disk only when it becomes necessary to do so, as more and more database changes are made, the disk-resident copy of the database becomes more and more out of date.
To recover the database, the roll-forward process combines a backup copy of the database with the records in the after-image log to redo all the changes that were made since the backup was created.
The information contained in the database is also used extensively by other state and federal natural resource agencies, local governments, university researchers, environmental and community associations, and various industry groups including oil and gas production and transmission; developers, realtors and builders; and dredging and navigation.
Consistency applications are submitted for projects by Federal Agencies, funded by federal monies, or occurring on Federal lands.
The consistencydatabase contains similar information to permits but many of the data fields are different, due to the different procedure to process consistencies.
Feeds |
Contact