Transaction Log Restore error

  • *Phew!* At least I can rest that I'm not doing anything wrong!

    Fortunately this is on Development, the only impact as fgar as I'm concerned is that no real changes can be done to the production server during a live run, which is something I'm trying to enforce anyway, so it's more ammo for me.

    Thanks hthan, very much appreciated


    ---------------------------------------
    It is by caffeine alone I set my mind in motion.
    It is by the Beans of Java that thoughts acquire speed,
    the hands acquire shaking, the shaking becomes a warning.
    It is by caffeine alone I set my mind in motion.

  • I do full backup every night at 11:00pm. So if the change is urgent, I do log backup, apply the change, and do a full backup. If its't urgent, I will schedule it to run after the last log backup at 10:45pm. My concern is does the problem happen to log shipping in SQL Enterprise version? If this is true then how can we live with it if a company purchased SQL EE instead of Std. version just because of the need of log shipping?

Viewing 2 posts - 16 through 16 (of 16 total)

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