 |
Why can a failure in a database environment be more serious than one in a non-database environment? |
[Edit] |
Database failures for Production envionments could be downtime for the database (data cannot be retrieved or uploaded) or a data loss in which a recovery needs to be performed, which also equates to downtime until the data is recovered. Businesses equate downtime to $$$ loss.
It is a database administrator's job to ensure the database is designed for minimal downtime--the recovery is measured in "MTR" (meantime to recovery). What's the fastest way the data can be restored? A full recovery? A point in time? (roll the data up right before the data loss occurred). This must be done carefully through communcation with the individuals where the data loss occurred. If the DBA is given the wrong time and the data is rolled forward beyond the corruption point, then the recovery must be started again.
There is much more to this subject.......based on each company's database, design, data, etc.
First answer by Ppyles. Last edit by Ppyles. Contributor trust: 116 [recommend contributor]. Question popularity: 11 [recommend question]
|
Research your answer: |
Answers.com > Wiki Answers > Categories > Technology > Computers > Computer Databases > Why can a failure in a database environment be more serious than one in a non-database environment?
Our contributors said this page should be displayed for the questions below. (Where do these come from ) |
| If any of these are not a genuine rephrasing of the question, please help out and edit these alternates. |
