February 18, 2008 at 2:56 pm
we have servers that are in production now and I have a task to move those databases to a remote server through FTP. In the remote server we will like to have all the databases with there transactions applied and up to date. At the same time I will like to know when any of the transaction logfiles is applied or failed to be applied on the remote server.
I intend to ftp the backup database file over to the remote server. Restore the backup with norecover. Setup logshipping between the servers to ftp the transaction logs and apply them.
The question I have is how can I know when any transaction fails.
February 18, 2008 at 3:46 pm
Do you mean transaction failure or a failure to restore one of the transaction logs? Or a failure to ftp one of the transaction logs?
You could setup a log shipping monitor (see BOL). Or you could modify the log shipping job(s) to send an email on step failure (would require either MAPI client on SQL Server, ick, or setup SMTP access - stored proc for SQL Server, SMTP relay permissions to an email server).
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
February 18, 2008 at 4:16 pm
I mean transaction log shipping failures that are not applied to the destination server.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply