<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SQL Recovery &#187; SQL Recover</title>
	<atom:link href="http://www.sqlrecovery.org/blog/tag/sql-recover/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sqlrecovery.org/blog</link>
	<description>SQL database recovery tool to recover mdf files from sql server.</description>
	<lastBuildDate>Fri, 13 Aug 2010 08:01:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Dealing with error 5171 in SQL</title>
		<link>http://www.sqlrecovery.org/blog/dealing-with-error-5171-in-sql/</link>
		<comments>http://www.sqlrecovery.org/blog/dealing-with-error-5171-in-sql/#comments</comments>
		<pubDate>Mon, 03 May 2010 05:22:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Database Recovery]]></category>
		<category><![CDATA[ms sql data recovery]]></category>
		<category><![CDATA[mssql database recovery]]></category>
		<category><![CDATA[repairing corrupt SQL database]]></category>
		<category><![CDATA[SQL Recover]]></category>
		<category><![CDATA[SQL recovery software]]></category>
		<category><![CDATA[sql server database recovery]]></category>

		<guid isPermaLink="false">http://www.sqlrecovery.org/blog/?p=57</guid>
		<description><![CDATA[<p>When  a user works with MS SQL Server 2005 and creates a report, he may  face technical problems. Windows server may restart due to power  failure and the user gets a screen prompting for the reason and  information for restart of Server. Due to this OS issue, the SQL  database becomes <a href='http://www.sqlrecovery.org/blog/dealing-with-error-5171-in-sql/' rel="nofollow">read more...</a></p>]]></description>
			<content:encoded><![CDATA[<p>When  a user works with MS SQL Server 2005 and creates a report, he may  face technical problems. Windows server may restart due to power  failure and the user gets a screen prompting for the reason and  information for restart of Server. Due to this OS issue, the SQL  database becomes <a href='http://www.sqlrecovery.org/blog/dealing-with-error-5171-in-sql/' rel="nofollow">read more...</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.sqlrecovery.org/blog/dealing-with-error-5171-in-sql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clustered Index corruption in MS SQL Server Database</title>
		<link>http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/</link>
		<comments>http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 05:51:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Database Recovery]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[SQL Recover]]></category>
		<category><![CDATA[SQL Recovery]]></category>

		<guid isPermaLink="false">http://www.sqlrecovery.org/blog/?p=36</guid>
		<description><![CDATA[<p>In  SQL Server, a database called tempdb is allocated for worktable /  #temp table usage. Sometimes when the tempdb exceeds its maximum size  limit, it starts behaving in weird manner. Possibilities of database  corruption are very high when size of tempdb is larger than it should  be, as when <a href='http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/' rel="nofollow">read more...</a></p>]]></description>
			<content:encoded><![CDATA[<p>In  SQL Server, a database called tempdb is allocated for worktable /  #temp table usage. Sometimes when the tempdb exceeds its maximum size  limit, it starts behaving in weird manner. Possibilities of database  corruption are very high when size of tempdb is larger than it should  be, as when <a href='http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/' rel="nofollow">read more...</a></p>]]></content:encoded>
			<wfw:commentRss>http://www.sqlrecovery.org/blog/clustered-index-corruption-in-ms-sql-server-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
