2009-02-19
3,246 reads
2009-02-19
3,246 reads
This script uses the system backup history to run a differential backup and place it in the directory of the last full backup.
2009-03-06 (first published: 2009-02-12)
641 reads
Logging and recovery are critical parts of SQL Server, but they are often poorly understood. Paul Randal gives an overview of how the logging and recovery features work in SQL Server and explains the transaction log and recovery models to help you maintain a better database.
2009-01-23
3,187 reads
2009-01-14
3,608 reads
2008-12-18
3,265 reads
This article shows how the COPY_ONLY clause can be used to ensure that an ad-hoc database backup do not break the backup sequence
2008-12-18
3,341 reads
2008-12-17
3,693 reads
2008-12-16
3,788 reads
2008-12-11
3,817 reads
Save the transaction log and truncate the file to prevent Tlogs FULL Error
2008-12-16 (first published: 2008-11-17)
2,701 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