2025-05-12
275 reads
2025-05-12
275 reads
2025-04-28
403 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)
7,930 reads
2020-12-10
419 reads
2018-06-28
869 reads
Get Logshipping report only when secondary is more than certain time behind Primary.
2017-11-14 (first published: 2017-10-27)
475 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,513 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,086 reads
A look at a SQL script solution that can help you easily fail over and back from log shipping scenarios.
2018-12-14 (first published: 2015-09-08)
3,716 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers