Use transaction logs to recover data loss caused by incorrect update and delete operations

Many of you may have encountered the following problems:
If the update or delete statement does not include the WHERE clause, or the WHERE clause is not accurate enough, the execution may cause serious consequences,
In this case, data recovery can only be performed using the backup of transaction logs. Therefore, if your SQL statement does not have a full database backup
Or the log cannot be backed up (the truncate log on checkpoint option is 1), so data cannot be restored, or
Only the data of the last backup can be restored.

The following describes how to restore data:
1. If a full-Database Backup (or multiple differential or incremental backups exist) exists before the misoperation, the first thing to do is
Perform a log backup (if you set trunc. Log On chkpt to 1 to prevent the log file from becoming larger)
Backup log dbname to disk = "FILENAME"
2. Recover a full-database backup. Use with norecovery. If there are other differences or incremental backups, recover them one by one.
Replay
Restore database dbname from disk = "FILENAME" with norecovery
3. Restore the last log backup, that is, the log backup you just created. Specify the recovery time point to the time before the misoperation.
Restore log dbname from disk = "FILENAME"
With stopat = "date_time"

These operations can be completed in the SQL Server Enterprise Manager, which is not difficult...

Of course, if the misoperation involves operations that do not remember logs, such as truncate table and select into, then there is no farli.
Use the above method to restore Data