开头日记备份(国外英语资料).docVIP

结尾日志备份(国外英语资料) The end log backup captures the tail of the log, even if the database is offline, corrupted, or missing data files. This may result in the restore information command and MSDB generating incomplete metadata. But only the metadata is incomplete, and the captured logs are complete and available. If the end log backup contains incomplete metadata, the has_incomplete_metadata in the backupset table is set to 1. In addition, in the output of RESTORE HEADERONLY, HasIncompleteMetadata will be set to 1. If the metadata in the end log backup is not complete, the backupfilegroup table will lose most of the relevant information about the file group at the end of the log backup. Most backupfilegroup tables are NULL; Only the following columns make sense: backup_set_id filegroup_id The type type_desc is_readonly Do not use the end log backup to perform the restore The reduction plan for the end log backup includes the following: Restore the database to a certain point in the previous log backup. If you RESTORE a database and specify STOPAT, STOPATMARK, or STOPBEFOREMARK in each of the RESTORE statements in the RESTORE order, you do not have to do the closing log backup. Restore the database to the previous point If you want to use the Transact - SQL restore to a particular point in time, please refer to how to restore to a particular point in time (Transact - SQL), back to mark the transaction or restore to the log sequence number (LSN). To use SQL Server Management Studio, see how to restore to a certain point (SQL Server Management Studio) or how to restore the database to the transaction (SQL Server Management Studio). Restore the database copy to the new location. When you restore database, only the database to restore to a different server instance, only can use the same database name, for example, to create a mirror image database is used for database or create a secondary database used for log shipping. If you move the database on the same server instance,