Back in April Steve Jones wrote up a disaster at work. Andy had one this week and wrote up the story too. Copy cat! Pretty soon everyone will be having a disaster and writing a story about it! Give these guys credit for letting you see what happens when it ALL goes bad. Disaster recovery is hard to sell and hard to do, reading the article might give you an idea that will save you some time and/or data one day.
This week we highlight the practice of being prepared for disasters at SQLServerCentral.
As part of Simple-Talk's long-running Cribsheet series, they asked William Brewer to write a guide to deployment that described in general terms what is involved in the deployment of a database application, and the sort of issues you're likely to come up against.
There is a certain paradox in being advised to expect the unexpected, but the DBA must plan and prepare in advance to protect their organisation's data assets in the event of an unexpected crisis, and return them to normal operating conditions. To minimise downtime in such circumstances should be the aim of every effective DBA. To plan for recovery, It pays to have the mindset of a pessimist.
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.
By Zikato
When I'm looking at a query, I bet it's bad if I see... a...
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
The DBA life is fraught with pain. Those battles that we endure are mostly...
Wa:0821-4447-7715 Wisma Asia, Jl. Letjen S. Parman No.Kav. 79, RT.4/RW.9, Kota Bambu Sel., Kec....
Comments posted to this topic are about the item A Quick Second Opinion
Comments posted to this topic are about the item Five Intelligent Query Processing Features...
On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?
See possible answers