October 28, 2004 at 10:13 pm
I am testing out Simple Log Shipping.
Can anyone confirm there is a bug in sp_ShipLog?
The log shipping runs forever, regardless of the setting of the @HourDuration parameter.
In sp_ShipLog I cannot see where the timestamp controlling the main WHILE loop is incremented - this would be one explaination for the infinite loop.
October 29, 2004 at 8:26 am
Simple log shipping? You must mean this.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
October 29, 2004 at 4:23 pm
It looks like your referring to the LiteSpeed simple log shipping scripts. We do not provide a procedure called sp_logship but do have simple log shipping scripts and an @hourduration parameter.
The @hourDuration parameter is used to set the end of the log shipping job in the following line:
-- SET the end date to be the current hour plus the end hour parameter
SET @EndDateTime = dateadd(hour, @HourDuration, @StartDateTime)
We then start a while look that keeps running untill the following condition is met:
WHILE @NextBackupDateTime < @EndDateTime
BEGIN
If this is not what you mean than let me know but the following code is in the prc_SLS_LS_Primary stored proc involved in simple Litespeed Log Shipping.
October 30, 2004 at 9:48 pm
I am refering to SLS as provided in the Microsoft SQL Server 2000 Resource kit, not MiniSQLBackup or LiteSpeed.
Changing the line
WHILE @StartDateTime < @EndDateTime to
WHILE @NextBackupDateTime < @EndDateTime
looks like it will fix the problem.
Thanks
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply