What if we did crazy things with log shipping, like using it for scale out reporting? And stick it behind a load balancer? For big monster terabyte-plus databases, it can work like a kind of pool of Always On readable secondaries.
Even a classic, well known tool like log shipping has gotchas. Learn what tricks you are better off avoiding and how you can handle special environments.
Log shipping is great, but if you change a lot of data your secondaries might get behind. Learn some tricks that can save a lot of pain in catching up a slow secondary.
Sometimes you do get to fail over gracefully. If you plan this out right, you can save a bunch of time and effort and not have to set up your log shipping from scratch!
We don’t always get to choose when we’re going to fail over. Learn what you need to look out for when you have to fail over unexpectedly with log shipping.
Get an overview of how log shipping works, different modes available, and pros and cons of this classic feature. Looking for an option for a free lab to play around in? Want a link to specific steps to setting up transaction log shipping? Curious if there’s any built in reports, or interested in more reading?…