<?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>The Pythian Blog &#187; SQL Server 2005</title>
	<atom:link href="http://www.pythian.com/news/tag/sql-server-2005/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:54:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>using NOLOCK hint</title>
		<link>http://www.pythian.com/news/29097/using-nolock-hint/</link>
		<comments>http://www.pythian.com/news/29097/using-nolock-hint/#comments</comments>
		<pubDate>Thu, 08 Dec 2011 18:41:47 +0000</pubDate>
		<dc:creator>goswami</dc:creator>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[performance tuning]]></category>
		<category><![CDATA[SQL Server 2005]]></category>
		<category><![CDATA[SQL Server Administration]]></category>
		<category><![CDATA[Table Hints]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=29097</guid>
		<description><![CDATA[Use NOLOCK hint to avoid block &#8211; this is what I have often heard/see in many forums I participate in, during local user group events and meetings. I have always advised that its not that good idea to use hints, as it may cause data corruption and blocking. And anyways, there are many things that [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/29097/using-nolock-hint/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL server: Create missing indexes with unmessing names</title>
		<link>http://www.pythian.com/news/28117/sql-server-create-missing-indexes-with-unmessing-names/</link>
		<comments>http://www.pythian.com/news/28117/sql-server-create-missing-indexes-with-unmessing-names/#comments</comments>
		<pubDate>Mon, 14 Nov 2011 13:10:39 +0000</pubDate>
		<dc:creator>Mohammed Mawla</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[SQL Server 2005]]></category>
		<category><![CDATA[sql server 2008]]></category>
		<category><![CDATA[SQL server performance]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=28117</guid>
		<description><![CDATA[If you do any performance tuning , and everyone do some day, then you&#8217;ll come to a point where you want to know if your tables have sufficient indexes to serve the queries fast. Starting with SQL server 2005 , engine tracks indexes usage , through query optimizer, and can now determine if a query [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/28117/sql-server-create-missing-indexes-with-unmessing-names/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Backups in SQL Server 2005/2008, Part 1: The Basics</title>
		<link>http://www.pythian.com/news/3099/backups-in-sql-server-20052008part-1-the-basics/</link>
		<comments>http://www.pythian.com/news/3099/backups-in-sql-server-20052008part-1-the-basics/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 20:56:04 +0000</pubDate>
		<dc:creator>Chris Presley</dc:creator>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[backups]]></category>
		<category><![CDATA[basics]]></category>
		<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[fundamentals]]></category>
		<category><![CDATA[refresher]]></category>
		<category><![CDATA[SQL Server 2005]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=3099</guid>
		<description><![CDATA[This is the first post in a series dedicated to exploring the backup and availability options in SQL Server 2005 and 2008. It is aimed at anyone unfamiliar with the database backup options in SQL Server 2005 and 2008. I&#8217;m not going to explore every single option or scenario, the goal is to give you [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/3099/backups-in-sql-server-20052008part-1-the-basics/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>SQL Server 2005: Automating Database Movement</title>
		<link>http://www.pythian.com/news/1432/sql-server-2005-automating-database-movement/</link>
		<comments>http://www.pythian.com/news/1432/sql-server-2005-automating-database-movement/#comments</comments>
		<pubDate>Mon, 12 Jan 2009 18:39:02 +0000</pubDate>
		<dc:creator>Chris Presley</dc:creator>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Automate Database Movement]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[restore]]></category>
		<category><![CDATA[SQL Server 2005]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1432/sql-server-2005-automating-database-movement</guid>
		<description><![CDATA[Let&#8217;s say for you want to move a database from one environment (possibly production) to another (possibly development) on a semi-regular basis. After about the 10th time doing it manually, you&#8217;re ready to automate the process. But how? That&#8217;s what I intend to help with in this post. For this example, I&#8217;m running two Virtual [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1432/sql-server-2005-automating-database-movement/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to Minimize Downtime When Moving to a New SQL Server Environment</title>
		<link>http://www.pythian.com/news/1159/how-to-minimize-downtime-when-moving-to-a-new-sql-server-environment/</link>
		<comments>http://www.pythian.com/news/1159/how-to-minimize-downtime-when-moving-to-a-new-sql-server-environment/#comments</comments>
		<pubDate>Mon, 11 Aug 2008 18:35:45 +0000</pubDate>
		<dc:creator>Michelle Gutzait</dc:creator>
				<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[log-shipping]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[restore]]></category>
		<category><![CDATA[SQL Server 2000]]></category>
		<category><![CDATA[SQL Server 2005]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1159/how-to-minimize-downtime-when-moving-to-a-new-sql-server-environment</guid>
		<description><![CDATA[I am often asked what ways are there to minimize downtime when upgrading from SQL Server 2000 to SQL Server 2005, or when moving databases to a new (probably bigger and stronger) environment. Well, if you can afford having both&#8211;old environment and new environment in parallel&#8211;this task can be very easy and straightforward&#160;.&#160;.&#160;. Options First, [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1159/how-to-minimize-downtime-when-moving-to-a-new-sql-server-environment/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

