<?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>Data Recovery Blog &#187; MS SQL Server Recovery</title>
	<atom:link href="http://www.nucleustechnologies.com/datarecoveryblog/category/database-recovery/ms-sql-server-recovery/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nucleustechnologies.com/datarecoveryblog</link>
	<description>Data Recovery Software - Email Recovery - File Recovery Tools</description>
	<lastBuildDate>Thu, 05 Jan 2012 11:10:26 +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>Error: SQL Server &#8211; Error starting esri_sde service -93 DBMS error code: 18456</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/error-sql-server-error-starting-esri_sde-service-93-dbms-error-code-18456/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/error-sql-server-error-starting-esri_sde-service-93-dbms-error-code-18456/#comments</comments>
		<pubDate>Mon, 05 Oct 2009 09:46:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[Error: SQL Server - Error starting esri_sde service -93 DBMS error code: 18456]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=330</guid>
		<description><![CDATA[Whenever there is inconsistency with the password, the following error message is logged in the SDE error log after trying to start the ArcSDE service:
IDBInitialize::Initialize Failed
init_DB DB_instance_open_as_dba: -93
DBMS error code: [<a href="http://www.nucleustechnologies.com/datarecoveryblog/error-sql-server-error-starting-esri_sde-service-93-dbms-error-code-18456/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/error-sql-server-error-starting-esri_sde-service-93-dbms-error-code-18456/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to resolve SQL Error 2519?</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/how-to-resolve-sql-error-2519/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/how-to-resolve-sql-error-2519/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 07:08:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[How to resolve SQL Error 2519?]]></category>
		<category><![CDATA[mdf recovery]]></category>
		<category><![CDATA[SQL error 2519]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[sql repair]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=294</guid>
		<description><![CDATA[SQL Server is the most preferred relational database systems that enable organizations to reliably manage mission-critical information in easy manner. SQL Server offers many advantageous features to its users. One [<a href="http://www.nucleustechnologies.com/datarecoveryblog/how-to-resolve-sql-error-2519/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/how-to-resolve-sql-error-2519/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Windows could not start the SQL Server &#8211; SQL Error- 10022</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/windows-could-not-start-the-sql-server-sql-error-10022/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/windows-could-not-start-the-sql-server-sql-error-10022/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 09:47:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[SQL Error- 10022]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=285</guid>
		<description><![CDATA[MS SQL Server is a fast, powerful and reliable relational database management system used for storing any kind of data.  But sometimes installation of this useful application gets corrupt [<a href="http://www.nucleustechnologies.com/datarecoveryblog/windows-could-not-start-the-sql-server-sql-error-10022/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/windows-could-not-start-the-sql-server-sql-error-10022/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolving SQL Server Error 8942</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/resolving-sql-server-error-8942/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/resolving-sql-server-error-8942/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 11:28:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[SQL database recovery]]></category>
		<category><![CDATA[SQL database repair]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Error 8942]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=275</guid>
		<description><![CDATA[SQL Server is the most reliable, fast and effective relational database management system specially designed for the enterprise environment. This application efficiently manages the enterprise data in the form of [<a href="http://www.nucleustechnologies.com/datarecoveryblog/resolving-sql-server-error-8942/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/resolving-sql-server-error-8942/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting unmapped SQL error code 10038 when connecting to MS SQL</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/getting-unmapped-sql-error-code-10038-when-connecting-to-ms-sql/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/getting-unmapped-sql-error-code-10038-when-connecting-to-ms-sql/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 11:16:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>
		<category><![CDATA[unmapped SQL error code 10038]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=272</guid>
		<description><![CDATA[While using SQL Server for your storage needs, you may encounter one of the most common error:
â€œUnmapped SQL error code 10038 &#8211; Attempt to initiate new SQL server operation with [<a href="http://www.nucleustechnologies.com/datarecoveryblog/getting-unmapped-sql-error-code-10038-when-connecting-to-ms-sql/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/getting-unmapped-sql-error-code-10038-when-connecting-to-ms-sql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The system cannot self repair this error</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/the-system-cannot-self-repair-this-error/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/the-system-cannot-self-repair-this-error/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 06:18:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[SQL errors]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>
		<category><![CDATA[The system cannot self repair this error]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=225</guid>
		<description><![CDATA[â€œThe system cannot self repair this errorâ€ is the common SQL error message that pops-up quite often. Reason for this error message is primarily due to corrupt metadata in SQL [<a href="http://www.nucleustechnologies.com/datarecoveryblog/the-system-cannot-self-repair-this-error/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/the-system-cannot-self-repair-this-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Canâ€™t Find File: .myi &#8211; Mysql Error and Recovery</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/cant-find-file-myi-mysql-error-and-recovery/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/cant-find-file-myi-mysql-error-and-recovery/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 07:35:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA['Can't Find File: .myi']]></category>
		<category><![CDATA[mdf recovery]]></category>
		<category><![CDATA[MS SQL recovery]]></category>
		<category><![CDATA[sql repair]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=169</guid>
		<description><![CDATA[MySQL uses MyISAM as the default storage engine, which is based on older ISAM code but comprises many useful extensions. The MyISAM comprises three files having extensions- .frm, .MYI, and [<a href="http://www.nucleustechnologies.com/datarecoveryblog/cant-find-file-myi-mysql-error-and-recovery/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/cant-find-file-myi-mysql-error-and-recovery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Data Corruption in SQL Server and MDF Recovery</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/data-corruption-in-sql-server-and-mdf-recovery/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/data-corruption-in-sql-server-and-mdf-recovery/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 07:25:37 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[mdf corruptions]]></category>
		<category><![CDATA[mdf database recovery]]></category>
		<category><![CDATA[mdf recovery]]></category>
		<category><![CDATA[MS SQL recovery]]></category>
		<category><![CDATA[SQL database recovery]]></category>
		<category><![CDATA[SQL recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=166</guid>
		<description><![CDATA[Microsoft SQL Server, the most preferred back-end (database) utility among organizations because of its scalability, consistency, and familiarity with users. A user of SQL Server uses SQL Server Management Studio [<a href="http://www.nucleustechnologies.com/datarecoveryblog/data-corruption-in-sql-server-and-mdf-recovery/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/data-corruption-in-sql-server-and-mdf-recovery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Table Corrupt: Object ID 0, index ID 0, page ID (1:623). PageId in the page header = (0:0)</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/table-corrupt-object-id-0-index-id-0-page-id-1623-pageid-in-the-page-header-00/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/table-corrupt-object-id-0-index-id-0-page-id-1623-pageid-in-the-page-header-00/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 12:22:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[SQL 2005 recovery]]></category>
		<category><![CDATA[SQL database recovery]]></category>
		<category><![CDATA[SQL recovery]]></category>
		<category><![CDATA[SQL Server Recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=163</guid>
		<description><![CDATA[The DBCC DBREINDEX is a transactional-SQL command that reconstructs one or more indexes for a table in the SQL database file. Additionally, DBCC SHRINKDATABASE is a T-SQL command used to [<a href="http://www.nucleustechnologies.com/datarecoveryblog/table-corrupt-object-id-0-index-id-0-page-id-1623-pageid-in-the-page-header-00/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/table-corrupt-object-id-0-index-id-0-page-id-1623-pageid-in-the-page-header-00/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Recover from a corrupted transaction log file</title>
		<link>http://www.nucleustechnologies.com/datarecoveryblog/recover-from-a-corrupted-transaction-log-file/</link>
		<comments>http://www.nucleustechnologies.com/datarecoveryblog/recover-from-a-corrupted-transaction-log-file/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 10:19:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[MS SQL Server Recovery]]></category>
		<category><![CDATA[mdf recovery]]></category>
		<category><![CDATA[mdf repair]]></category>
		<category><![CDATA[recover from corrupt logs of SQL]]></category>
		<category><![CDATA[sql server data recovery]]></category>

		<guid isPermaLink="false">http://www.nucleustechnologies.com/datarecoveryblog/?p=135</guid>
		<description><![CDATA[MS SQL Server is the most ordinarily used database client, can be subjected to corruption due to various logical and physical reasons. Let us suppose a situation when you are [<a href="http://www.nucleustechnologies.com/datarecoveryblog/recover-from-a-corrupted-transaction-log-file/" class="fullarticle">read full article</a>]]]></description>
		<wfw:commentRss>http://www.nucleustechnologies.com/datarecoveryblog/recover-from-a-corrupted-transaction-log-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

