A SQL Server upgrade left a log shipping secondary unable to accept transaction logs. Re-seeding it without touching the primary or its mirror is straightforward in principle — drop, restore full + diff + log with NORECOVERY, hand back to the job — but three undocumented traps will stop you along the way. Here's what they are and how to get past them.
2026-10-14
1,038 reads
2025-05-12
325 reads
2025-04-28
440 reads
This article shows how we were able to migrate a TB size database to new storage with minimal downtime.
2024-01-01 (first published: 2021-02-24)
8,263 reads
2020-12-10
439 reads
2018-06-28
944 reads
Get Logshipping report only when secondary is more than certain time behind Primary.
2017-11-14 (first published: 2017-10-27)
536 reads
2016-05-11
4,469 reads
How to move a log shipping database to a new monitor server without removing and rebuilding the log shipping setup.
2016-04-04
2,568 reads
When you’re reading from a log shipped secondary, you want the duration of restores to be as short as possible. The sproc provided switches the restores to “NORECOVERY” mode, and then switch back to “STANDBY” at the end of the process.
2015-12-11 (first published: 2015-11-23)
3,182 reads
By Brian Kelley
Here is another short video (~ 15 minutes). This is by the author of...
By Steve Jones
I had a briefing for the 2026 PASS Data Community Summit, which is just...
Your AI is busy. But do you know what it's worth? Most companies can...
Comments posted to this topic are about the item SQL Server 2025 Server-level Roles
Comments posted to this topic are about the item Stairway to DAX and Power...
Comments posted to this topic are about the item AI Is Improving Security
In SQL Server 2022+, what does the ##MS_DatabaseConnector## role allow?
See possible answers