This is the part of the process which is likely to take longest to complete, depending on the size of your database Restore the latest SQL database backup and all log backup files up to the point in time where the data was last known to be correct, as a database with a different name on the same server Here is a diagram of the steps which will need to be performed to recover a single table from a backup: Of course, this is also true if you restore the entire database backup and then just copy out the specified table, so either way, this is something which will always have to be taken into account when performing a single table recovery. If you extract only one table from a backup, which is not at the same point of time as your current database, it might result in referential integrity being compromised. If I would have to guess at why Microsoft has not provided this functionality, I would have to say that it probably relates to integrity concerns. Restoring an entire backup can take a significant amount of time, and generally, when a table has been damaged to such an extent that a restore is required, the DBA will probably be experiencing pressure to get it done fast.More often than not, the rest of the database is fine, except that someone accidentally damaged or dropped a specific table.Why do DBA’s want this? Well, the reasons are simple: Of course, it is possible to retrieve the data of a specific table from a database backup, but you cannot do it without restoring the entire backup. When you ask a DBA what feature they would most like to see added to the SQL Server recovery functionality, they will undoubtedly say: “The ability to recover a single table from a database backup”.
0 kommentar(er)
