SQL Server is a database management system that stores user information in tables. If the table is corrupted, you may be asked to reload the data one table in the database without changing the contents of other tables. The obvious answer is to restore a backup copy of the database to put the database back to the state the environment was in before the corruption occurred, but the problem might be that other tables have been updated and the owners of that data don’t want to lose the good data to fix the bad data.
In SQL Server you can perform simple object level recovery by restoring a recent backup of the database to a different database server or instance, the replace the bad data with the data from the restored database. To complete this important task you must have good database backup. If you don’t have a backup taken before the corruption, then you can not perform this action using this method.
Another thing you need to consider is if you need to support this type of activity you must have a target server with enough free drive space to restore your backup. If your database is 1 TB in size, for example, while your backup might be compressed to save space you will need at least 1 TB of free space to restore a copy of your database. A lot of people don’t have that kind of free space readily available, so think about that as your write your incident recovery documentation.