2013-04-18 (first published: 2013-04-05)
1,462 reads
2013-04-18 (first published: 2013-04-05)
1,462 reads
The most critical task for all DBAs is to have a Backup and Recovery strategy that ensures, every day, that in the event of a disaster they can restore and recover any database, within acceptable limits for data loss and downtime. Even with all the required backups in place, it's easy to miss subtle failings in the overall plan that can, and eventually will, defeat your recovery plans.
2013-01-28
2,889 reads
Developing a backup procedure that makes sure you can do restores should be one of your top priorities as a DBA. In this article Greg Larsen discusses some of the concepts to consider when developing, building and testing a backup strategy.
2013-01-14
3,298 reads
During presentations about doing database backups and restores, there seem to be two two types of questions that are commonly asked, Those that come from the floor during the presentation, and those that are asked in private afterwards. These are sometimes more interesting, and challenging to answer well.
2012-12-11
3,466 reads
2012-12-07 (first published: 2012-11-19)
1,388 reads
You can download a free eBook from SQLServerCentral and Red Gate software on the most important task a SQL Server DBA or developer needs to understand.
2013-01-25 (first published: 2012-10-23)
12,771 reads
Grant takes a humorous (but completely serious) look at why you should be regularly verifying your backups. Get top tips for backup and recovery, and protect yourself when disaster strikes. Watch the video
2012-09-21
2,886 reads
Shawn McGehee discusses partial backups, how they're used, and how to avoid potential problems when restoring from a partial backup.
2012-05-15
3,016 reads
2012-02-21
2,428 reads
The majority of companies that suffer a major data loss subsequently go out of business. Wesley David remembers vividly the day when the organisation he worked for found that they couldn't restore their data, and the subsequent struggles that ensued. Shoulda-woulda-coulda.
2012-02-20
4,949 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