Recover truncated messages from the primary database log by replaying off-line transaction logs.
To do this, you must use the same sequence of create database and alter database commands when creating the temporary database as were used to create the original database.
Checking Loss for DS1.PDB from DS1.PDB date=Nov-01-1995 10:35am qid=0x01234567890123456789
sp_start_rep_agent temp_dbname, 'recovery', 'connect_dataserver', 'connect_database', 'repserver_name', 'repserver_username', 'repserver_password'
where connect_dataserver and connect_database specify the original primary data server and database.
RepAgent transfers data in the transaction log of the temporary recovery database to the original primary database. When RepAgent completes scanning the current transaction log, it shuts down.
Recovery of transaction log is complete. Please load the next transaction log dump and then start up the Rep Agent Thread with sp_start_rep_agent, with ‘recovery’ specified.
and perform the appropriate actions.
Execute admin who_is_down.
If the RepAgent reports “down,” load the next transaction log.
You are now ready to resume normal replication from the primary database.
rs_zeroltm data_server, database dbcc settrunc('ltm', 'valid')