1) when the database is completely different and the log backup is performed, the unused entries in the transaction log are deleted, and then the Log Explorer attempts to view the log, prompting Nologrecordersfoundthatmatchthefilter, when wouldyouliketoviewunfiltereddata is set to yes, you cannot see the record you just logged. If you do not select Delete transaction logs, the log is not active.
1) when the database is completely different and the log backup is performed, the unused entries in the transaction log are deleted, and then the Log Explorer attempts to view the log, prompting Nologrecordersfoundthatmatchthefilter, when wouldyouliketoviewunfiltereddata is set to yes, you cannot see the record you just logged. If you do not select Delete transaction logs, the log is not active.
1) completely different databases and log backup
Deleted non-active entries in the transaction log are selected during Backup.
When I try to view logs with Log explorer
Prompt No log recorders found that match the filter, wocould you like to view unfiltered data
Select yes to see the record.
If you do not select to delete non-active entries in the transaction log
When Log explorer is used to view logs, the Hong Kong server can view the original logs.
2) modified part of the data in one of the tables. At this time, Log explorer is used to view the logs, which can be used for Log recovery.
3) then recover the backup. (Note: log explorer is disconnected from the database or connected to other data,
Otherwise, the database is in use and cannot be recovered)
After the restoration, the VM, Hong Kong Vm, and then log explorer prompts No log recorders found that match the filter, wocould you like to view unfiltered data
If yes is selected, you cannot see the log record modified in 2. Therefore, the log cannot be restored.
3)
Do not use the SQL backup function to back up your logs.
The correct backup method is:
Stop SQL Service, copy data files and log files for file backup.
Start the SQL service and use log explorer to restore data.