<?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>Ben Morris. &#187; SQL Server</title>
	<atom:link href="http://www.ben-morris.com/category/sql-server/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ben-morris.com</link>
	<description>Web and digital development stuff.</description>
	<lastBuildDate>Mon, 30 Aug 2010 20:19:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Identity over-use: Surrogate vs Composite keys in SQL Server</title>
		<link>http://www.ben-morris.com/identity-surrogate-vs-composite-keys-in-sql-server</link>
		<comments>http://www.ben-morris.com/identity-surrogate-vs-composite-keys-in-sql-server#comments</comments>
		<pubDate>Sun, 13 Sep 2009 16:11:22 +0000</pubDate>
		<dc:creator>Ben Morris</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.ben-morris.com/?p=307</guid>
		<description><![CDATA[The SQL Server 'Identity' column is a handy way of ensuring a unique primary key, but I have noticed a tendency for some database designs to over-use it.]]></description>
		<wfw:commentRss>http://www.ben-morris.com/identity-surrogate-vs-composite-keys-in-sql-server/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Improving ASP.NET Performance: SQL Server Database access</title>
		<link>http://www.ben-morris.com/asp_net_sql_server_performance</link>
		<comments>http://www.ben-morris.com/asp_net_sql_server_performance#comments</comments>
		<pubDate>Tue, 12 Feb 2008 15:10:01 +0000</pubDate>
		<dc:creator>Ben Morris</dc:creator>
				<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.ben-morris.com/?p=25</guid>
		<description><![CDATA[Your database interactions are among the most expensive operations you’ll perform in an web application.There are a number of best practices that you should be following when coding a scalable application for SQL Server - here are some of the rules that I swear by.]]></description>
		<wfw:commentRss>http://www.ben-morris.com/asp_net_sql_server_performance/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Storing documents as XML in SQL Server 2005</title>
		<link>http://www.ben-morris.com/storing_documents_as_xml_in_sql_server</link>
		<comments>http://www.ben-morris.com/storing_documents_as_xml_in_sql_server#comments</comments>
		<pubDate>Tue, 12 Feb 2008 14:58:35 +0000</pubDate>
		<dc:creator>Ben Morris</dc:creator>
				<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.ben-morris.com/?p=21</guid>
		<description><![CDATA[When considering how to store documents in SQL Server database it is worth considering that a database is designed to store data, while a file system is designed for storing files. That said, there will be occasions where you will want to store documents in SQL Server. This isn’t just for the convenience of having [...]]]></description>
		<wfw:commentRss>http://www.ben-morris.com/storing_documents_as_xml_in_sql_server/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
