Reposted from: the software of movie explorer found relevant information on the Internet. I feel that it is quite good here and I will learn from it. Try again later. 1. Log Explorer for SQL Server v4.0.2
I recommend this software.
RegisterProgram(The compressed file has a registration machine)
Open Log Explorer File => attach log file-> Select Server and logon mode-> connect->
Select database> attach> browse> view log> In the left-side dialog box to view the log record.
Click View DDL commands. There are many drop table commands.
Click the "undo" button below to generate the table structure Statement (Create Table ....)
Click the "Salvage" button below to generate the insert Statement (insert into... values ....)
To restore the file, right-click the log record undo transation and choose Save file name and path> open the file and run it in the query analyzer.
T-SQLCodeYou can.
For example, if log is delete table where..., the generated file code is Insert table ....
Several Problems in Log Explorer
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
Log Explorer can be used to view 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, Log Explorer prompts no log recorders found that matches 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.
4) 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.
5) if the Log Recovery Model of your database is simple, it cannot be restored using log explorer.
6) Log Explorer must be installed on the SQL Server server on which the database is to be restored, or the server is installed on the SQL Server server, and the client is installed on the operating computer for data recovery.
2. If the data volume is large, a genuine Veritas is installed on the tape drive and cluster, which is a good way to restore data.
The following are important new features of the software:
· Disaster recovery drill (disaster recovery fire drill)-the ability to freely test, plan, and test disaster recovery plans without interrupting the production process.
· Cluster Simulator-you can test the application failover solution to verify the availability of the application and determine whether the application is based on the planned failover policy and application requirements, migrate to the most appropriate server.
· Global cluster option-it can be quickly and easily upgraded to any architecture when availability requirements are migrated from local to wide-area disaster recovery.
· Instant access to data replication-data can be accessed in real time while being copied, and only part of the available storage capacity of the customer is occupied.
· Volume replication advisor-accurately analyzes bandwidth requirements and ensures application optimization.
I will not describe it here because the installation software is easy to use. I have a multi-user version of the burned Veritas cluster server. If you need a colleague, you can find me to install and try it out.
The disadvantage of the software is that the price is expensive.
In addition, I have some data restoration experiences:
1. Usually, you need to perform hot backup, daily backup, monthly backup, annual backup, data replication, exception records, and so on. In case of data loss, you can be impatient.
2. If the disk is damaged or the database is deleted by mistake, you can use software such as easyrecovery or recover4all to restore the deleted or damaged files and recover the data.
3. If the network is disconnected from the replication, we recommend that you only manually create a batch of data to make up for the loss of data, generally, data similar to latitude (such as time and region) is selected.