Comprehensive Backup Script
These scripts were generated to standardize our SQL backup environments, and to remove backups from Maintenance Plans.
2011-12-22 (first published: 2008-01-29)
3,448 reads
These scripts were generated to standardize our SQL backup environments, and to remove backups from Maintenance Plans.
2011-12-22 (first published: 2008-01-29)
3,448 reads
Rodney Landrum presents a creative solution for dynamic reporting across all of his SQL Servers, based on use of Red Gate's SQL Backup and SQL Multi Script.
2008-01-22
3,370 reads
Procedure changes all databases' recovery mode to simple and shrinks them all (or at least it tries to).
2012-03-07 (first published: 2008-01-14)
3,917 reads
2012-08-03 (first published: 2008-01-09)
2,320 reads
2008-01-29 (first published: 2007-11-23)
1,967 reads
2011-09-09 (first published: 2007-11-19)
8,932 reads
From one of the SQL Server 2005 storage engine lead developers comes this look at the impact of using the NO_LOG and TRUNCATE_ONLY options.
2007-10-24
3,313 reads
Restore server/database users and roles from another server when we are restoring databases to another server.
2012-04-12 (first published: 2007-10-23)
3,114 reads
This script was designed to restore a backup of a SQL Server 2000 database from disk file to SQL Server 2005.Unfortunatelly the RESTORE will leave land mines for you to find the hard way, this script was updated to fix all that I have found:Change CONCAT_NULL_YIELDS_NULL ON, PAGE_VERIFY CHECKSUM, Compatibility level to 90, remove the […]
2007-09-14
4,527 reads
2011-06-01 (first published: 2007-09-02)
10,472 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