<?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>MSExchangeGuru.com &#187; Database Management</title>
	<atom:link href="http://msexchangeguru.com/category/db-mgmt/feed/" rel="self" type="application/rss+xml" />
	<link>http://msexchangeguru.com</link>
	<description>Learn Exchange the Guru way !!!</description>
	<lastBuildDate>Fri, 30 Jul 2010 06:45:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Named Props Quota in Exchange 2007, SP1 RU8 and beyond</title>
		<link>http://msexchangeguru.com/2010/07/30/named-props-quota-in-exchange-2007-sp1-ru8-and-beyond/</link>
		<comments>http://msexchangeguru.com/2010/07/30/named-props-quota-in-exchange-2007-sp1-ru8-and-beyond/#comments</comments>
		<pubDate>Fri, 30 Jul 2010 06:05:59 +0000</pubDate>
		<dc:creator>Kumar</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=559</guid>
		<description><![CDATA[Ratish post here has already detailed about Named Props Quota and the trouble it creates for the Admins in Exchange 2003 and 2007 and so, I am not going to dive into it now. But the good news is that Exchange 2007 SP1 RU7 and Exchange 2007 SP2 has got in some improvements, but at [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2010/07/30/named-props-quota-in-exchange-2007-sp1-ru8-and-beyond/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exchange 2007: Operation terminated with error -939586631 The restore environment information isn&#8217;t found or cannot be opened</title>
		<link>http://msexchangeguru.com/2010/07/27/e2k7-restore-939586631/</link>
		<comments>http://msexchangeguru.com/2010/07/27/e2k7-restore-939586631/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 18:27:25 +0000</pubDate>
		<dc:creator>Ratish Sekhar</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=553</guid>
		<description><![CDATA[Exchange 2007 restore process fails with the following error­­­­ -939586631 Operation terminated with error -939586631 The restore environment information isn&#8217;t found or cannot be opened. This issue had me think for 2 hours. Longest time any eseutil issue has taken. Internet never had a trace on any solution. Scenario Exchange 2007 SP2 database restored to [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2010/07/27/e2k7-restore-939586631/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exchange 2010 database recovery</title>
		<link>http://msexchangeguru.com/2010/05/23/exchange2010-recovery-database/</link>
		<comments>http://msexchangeguru.com/2010/05/23/exchange2010-recovery-database/#comments</comments>
		<pubDate>Sun, 23 May 2010 12:36:56 +0000</pubDate>
		<dc:creator>Ratish Sekhar</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=483</guid>
		<description><![CDATA[This article outline&#8217;s the steps to restore an exchange database in Exchange 2010, christened Recovery Database for DAG. 1. Create 2 folders: Database              &#8211;&#62; D:\Recovery\Database Transaction Logs   &#8211;&#62; D:\Recovery\Logs 2. Now restore the database which is to be recovered and the subsequent logs exactly to the above location 3. Now follow steps 1-7 mentioned in the [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2010/05/23/exchange2010-recovery-database/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Restore Database of Server A to Server B</title>
		<link>http://msexchangeguru.com/2009/09/08/restore-database-of-server-a-to-server-b/</link>
		<comments>http://msexchangeguru.com/2009/09/08/restore-database-of-server-a-to-server-b/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 07:34:54 +0000</pubDate>
		<dc:creator>Ratish Sekhar</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=237</guid>
		<description><![CDATA[In Exchange, it a known issue that we cannot mount or restore database of one server to another. The Database Portability feature in makes it possible in Exchange 2007 but for Exchange 2003 there is a procedure to tackle this situation. Before I get into the topic, will talk a bit about Database Portability feature [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2009/09/08/restore-database-of-server-a-to-server-b/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Event id: 9667 &#8211; When database reaches maximum limit of named properties or replica identifiers</title>
		<link>http://msexchangeguru.com/2009/09/04/event-id-9667/</link>
		<comments>http://msexchangeguru.com/2009/09/04/event-id-9667/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 07:50:52 +0000</pubDate>
		<dc:creator>Ratish Sekhar</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=216</guid>
		<description><![CDATA[So what is this Named Property anyways ???  Most objects for MAPI specification are represented as properties which are PropIDs.  Range of these PropIDs can vary from 1~65535 (0xFFFF). There are 3 ranges which differentiates a PropID and anything which falls within range 32768 (0&#215;8000 or 8K)is called a standard property.  Now comes our hero, [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2009/09/04/event-id-9667/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Bad Checksum on Exchange Database</title>
		<link>http://msexchangeguru.com/2009/07/13/checksum-error/</link>
		<comments>http://msexchangeguru.com/2009/07/13/checksum-error/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 00:54:48 +0000</pubDate>
		<dc:creator>Meera Nair</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=45</guid>
		<description><![CDATA[A Bad checksum error on an Exchange Database indicates a database corruption. If you notice the same, consider moving mailboxes ASAP if the stores are still mounted or perform a repair if it went down. &#8211; Meera Nair]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2009/07/13/checksum-error/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exchange Database Recovery &#8211; Using eseutil commands</title>
		<link>http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/</link>
		<comments>http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/#comments</comments>
		<pubDate>Sun, 12 Jul 2009 20:00:07 +0000</pubDate>
		<dc:creator>Meera Nair</dc:creator>
				<category><![CDATA[Database Management]]></category>

		<guid isPermaLink="false">http://msexchangeguru.com/?p=35</guid>
		<description><![CDATA[The real job of an exchange administrator is to maintain high availability when it comes to a messaging environment. Below mentioned processes are not done on a day to day basis, but understanding how the process works is mandatory for every exchange administrator. A step by step walk-through of procedure to be followed when exchange [...]]]></description>
		<wfw:commentRss>http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>
