Cloud Concerns
Security is a concern in the cloud, but should it be your number one concern? Steve Jones notes that business continuity might be a bigger issue.
Security is a concern in the cloud, but should it be your number one concern? Steve Jones notes that business continuity might be a bigger issue.
Functionality to help maintain a Disaster/Recovery (D/R) Environment synchronized with production is introduced and the associated challenges are discussed.
There are some skills which are extensions of your instincts, and which you can only learn though years of experience. Matt Simmons has this brought home by the fact that he was recently minutes away from a data-loss disaster, and he doesn't quite know how he prevented it.
A disaster can easily lead to another disaster. Can you respond to multiple problems? Have you even considered the cascade effects of a large disaster?
A real world account of disaster recovery. (This article is being republished after the recent hurricane that hit the US East Coast).
The backup and restore system in SQL Server hasn't changed a great deal over the years despite a huge growth in the typical size of databases. When disaster strikes, and an important service is taken offline while a restore is performed, there is often time to reflect on whether it might be possible to design databases for a more rapid recovery of the most critical parts of a database application.
A suggested design for creating flight schedules makes querying easy. Includes basic airport and airlines data. Get started now with this tricky query problem.
Part of an effective response to a disaster situation is practice and testing of your skills and procedures. Steve Jones reminds us this is important today.
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.
This paper provides a foundation for understanding data replication as well as a discussion of the criteria for selecting an appropriate replication technology.
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