2017-07-20
992 reads
2017-07-20
992 reads
Practice makes perfect. That’s true of everything, including disaster recovery. If you aren’t already testing your DR plan, you should be - here’s what you need to know to get started.
2017-07-10
690 reads
2017-01-26
1,232 reads
Part 2, a more in depth look at An alternative approach to disaster recovery and backup strategies using PolyBase.
2015-08-11
2,080 reads
Big data applications are not usually considered mission-critical: while they support sales and marketing decisions, they do not significantly affect core operations such as customer accounts, orders, inventory, and shipping. Why, then, are major IT organizations moving quickly to incorporating big data in their disaster recovery plans?
2015-04-29
9,397 reads
In the first in a series on the practicalities of using the Microsoft Azure Platform for the SQL Server professional, Buck Woody shows that, whatever your version of SQL Server, there is a way of storing offsite backups in the cloud.
2014-08-11
9,549 reads
A corollary to Murphy's Law states that disaster is most likely to strike when your senior people are out of the office.
2013-08-01
4,236 reads
Today's complex systems are too large to be able to rely on any DBA's memory for knowledge of each component, and its configuration options and settings.
2013-07-25
4,301 reads
Sometimes recovery simply entails rerunning a failed process.
2013-07-19
3,818 reads
Data Protection and Disaster Recovery (DR) are IT tasks that seldom get the same level of attention as development… until disaster strikes. Only if planning is adequate can an organisation be resilient in the face of unexpected problems. There are several steps that are needed to achieve an adequate DR process and the ability to restore business operations after a disaster.
2013-04-18
3,227 reads
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
Fare Labs' shelf life testing facility has been accredited by the NABL. The best...
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...
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