﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Articles tagged Administering, Strategies, Disaster Recovery, Miscellaneous</title><link>http://www.sqlservercentral.com/</link><description>Articles tagged Administering, Strategies, Disaster Recovery, Miscellaneous posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Integrating SQL LiteSpeed in your existing Backup Infrastructure</title><description>This articles makes the case for using SQL LiteSpeed over other backup solutions and presents some notes about why the DBA should manage backups rather than offloading to network administration.
</description><guid>http://www.sqlservercentral.com/articles/Administering/integratingsqllitespeedinyourexistingbackupinfrast/986/</guid><pubDate>2003/05/12</pubDate><link>http://www.sqlservercentral.com/articles/Administering/integratingsqllitespeedinyourexistingbackupinfrast/986/</link></item><item><title>Another Disaster (Almost)</title><description>Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
</description><guid>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</guid><pubDate>2003/01/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</link></item></channel></rss>