We have SQL Server 2012. A service we use requires us to use log shipping, however we are tired of having users being kicked offline every 15 minutes.

Are there any creative ways to get around this (I believe it cannot be stopped) but perhaps setting up replication & log shipping is that possible?

Somehow having two instances of the same database so when one goes down for log shipping the secondary is automatically used.

Just looking for any creative way to get around users being kicked off during log shipping.

  • Are you saying that the user are being kicked off from A: the database form which the logs are being shipped from or B: kicked off the database to which the logs are being shipped ? – armitage Jul 9 '15 at 23:17
  • 1
    Highly recommend to read, understand and implement it first in test environment - readable secondaries on a budget written by @aaronbertrand. – Kin Shah Jul 10 '15 at 1:46
  • @armitage the database the logs are being applied to. We can't touch the server they are being shipped from. – James Wilson Jul 10 '15 at 14:35
  • @kin I read through a lot of it and trying to understand it. Is this solution possible if we can't touch the database that sens us logs? That is all handled via third party. They FTP us the logs. It sounded like in the article we needed the "boss" server on our end. – James Wilson Jul 10 '15 at 15:06
  • @JamesWilson then you are going to have problems. Its something that you should be fully managing - if you want to go for that solution. If you want the secondary to be available, why cant you choose transactional replication ? – Kin Shah Jul 10 '15 at 15:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.