<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Best Practice for Database Redundancy with DBXL</title><link>https://www.infopathdev.com:443/blogs/jim/archive/2009/05/18/best-practice-for-database-redundancy-with-dbxl.aspx</link><description>Large enterprises generally have redundancy mechanisms in place for critical SQL databases and are managed by an IT staff. For those without the large IT staff to manage your systems, you may still need something more than nightly backups. For high-availability</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Twitted by InfoPathDev</title><link>https://www.infopathdev.com:443/blogs/jim/archive/2009/05/18/best-practice-for-database-redundancy-with-dbxl.aspx#41923</link><pubDate>Thu, 21 May 2009 16:16:57 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:41923</guid><dc:creator>Twitted by InfoPathDev</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;Twitted by InfoPathDev&lt;/p&gt;
&lt;img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=41923" width="1" height="1"&gt;</description></item></channel></rss>