Everyone wants a highly available system, but achieving 4 or 5 9s of uptime is hard to do. Especially when you have cost limitations. New author Mark Cook takes a look at how his company analyzed the challenges and which method they chose along with some implementation details.
2006-05-25
5,300 reads
Not the traditional overview here. Steve Jones takes a look at the various high availability technologies from a different perspective.
2006-05-24
17,992 reads
Disaster recovery solutions is always a concern with SQL Server and when a new or unique solution comes up, we like to get it out there. New author Kevin Parks brings us a look at his way of using a USB hard drive and Windows PE to ensure recovery.
2006-05-18
8,737 reads
Ensuring the availability of your database servers is becoming more important all the time. Fortunately you have more choices than ever. Bilal Ahmed looks at some of the possible solutions available for SQL Server.
2006-04-26
5,436 reads
Testing is key to ensuring a process actually works when it comes time to implement, rather than finding out when time may be of the essence. This holds true for testing SQL Server restores as well.
2006-04-24
2,625 reads
Building a highly fault tolerant and available SQL Server is expensive and difficult. This brings about unique challenges for small businesses who often lack the resources of large enterprises. Bilal Ahmed and Shivan Bindal discuss the various ways of building redundancy and the challenges of each.
2006-02-21
5,989 reads
Building a highly available system is hard. This short white paper from Sonasoft shows some of the differences between a cluster and their standby server product.
2005-10-28
10,574 reads
The second installment of this series discussed the cost of maintaining systems with various levels of downtime, ways data can be lost, and what constitutes a backup. In this installment, I discuss how to configure your hardware to minimize the need to restore a backup.
2005-09-29
2,398 reads
2005-09-16
2,193 reads
2005-09-06
2,093 reads
By Steve Jones
I come to Heathrow often. Today is likely somewhere close to 60 trips to...
By Brian Kelley
If your organization is spending money, then meaningful results are a must. Pen testing...
I’m starting a webinar series about SQL Server indexing with the fine folks of...
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