The Case of the Shrinking CFO, err Database
Shrink SQL Server databases quickly and with virtually no contention.
2017-12-25 (first published: 2015-08-17)
4,355 reads
Shrink SQL Server databases quickly and with virtually no contention.
2017-12-25 (first published: 2015-08-17)
4,355 reads
How to delete millions of rows with virtually no contention.
2015-09-04 (first published: 2013-03-06)
28,361 reads
A SQL Server migration with minimal business impact while synchronizing schema and data.
2013-09-23
3,376 reads
Your production SQL Server transactional replication just failed and the business impact is critical. How do you get replication restored in minutes?
2013-05-30
8,597 reads
This article will show you one way to quickly restore SQL Server replication with huge tables.
2012-05-18
7,753 reads
How do you delete millions of rows with minimal impact to the business? This article gives you a way to accomplish the removal of old data.
2012-03-06
15,485 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