Post reply

Log Shipping in SQL Server 2005

  • November 20, 2007 at 4:20 am

    #180584

    I have just configured log shipping in SQL Server 2005 but there is latency between the backup of the tlog on the primary server and the copy of the tlog to the secondary server. There is also latency between the copy of the tlog to the secondary server and the restore of the tlog to the secondary database.

    My question is how do I get the backup job to trigger the copy job on the secondary server and also the copy job to trigger the restore job.

    This way there will be no latency and the system will be up to date.

    Please help....

    Thanks,

  • November 20, 2007 at 4:36 am

    #752591

    Are u using any monitor server for logshipping...

  • November 20, 2007 at 4:40 am

    #752593

    We are not using a monitor server

  • November 21, 2007 at 5:02 am

    #753041

    I have worked out how to do this using the SQLCMD utility within SQL2005.

    We used to use iSQL and needed a new way.

    All sorted now.

    Thanks,

  • November 22, 2007 at 7:32 am

    #753411

    don't leave us in suspense, please post and share your solution.

    I would have thought the simplest way though would be just to change the execution times of the sqlagent jobs controlling log shipping.

    Having a delay before loading the logs is not necessarily a bad thing, could give you an unspoilt copy of the database if say someone deleted data they did not intend to............

    ---------------------------------------------------------------------

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply