<?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 Server Performance &#187; Jude O&#8217;Kelly</title>
	<atom:link href="http://www.sql-server-performance.com/author/judeokelly/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Wed, 15 May 2013 08:10:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Primer on Selecting Data Using Entity Framework</title>
		<link>http://www.sql-server-performance.com/2013/selecting-data-entity-framework-find-firstordefault-single/</link>
		<comments>http://www.sql-server-performance.com/2013/selecting-data-entity-framework-find-firstordefault-single/#comments</comments>
		<pubDate>Thu, 07 Feb 2013 06:46:37 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3564</guid>
		<description><![CDATA[This question about selecting data using Entity Framework on StackOverflow got me thinking that a lot of LINQ to Entities code samples show very little consistency in how data is selected. Find(), Single(), SingleOrDefault(), First(), and FirstOrDefault() are often used interchangeably. The first issue to address is using Where() in the data selection statement. Where() [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/selecting-data-entity-framework-find-firstordefault-single/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebSite Performance Optimization &#8211; Core Concepts</title>
		<link>http://www.sql-server-performance.com/2012/website-performance-optimization-core-concepts/</link>
		<comments>http://www.sql-server-performance.com/2012/website-performance-optimization-core-concepts/#comments</comments>
		<pubDate>Mon, 26 Nov 2012 08:56:25 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3414</guid>
		<description><![CDATA[[Note : This was originally published on my personal blog at JudeOKelly.com. However, since the topic is on performance optimization and many SQL Server installations are the backend for a website/webapp I am cross posting this.] When it comes to performance tuning a site, there are a multitude of possible optimizations so I thought it [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/website-performance-optimization-core-concepts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ASP.NET MVC Security &#8211; Guarding Against Mass Assignment Vulnerability</title>
		<link>http://www.sql-server-performance.com/2012/asp-net-mvc-security-guarding-against-mass-assignment-vulnerability/</link>
		<comments>http://www.sql-server-performance.com/2012/asp-net-mvc-security-guarding-against-mass-assignment-vulnerability/#comments</comments>
		<pubDate>Mon, 05 Nov 2012 05:46:02 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[ASP.NET MVC]]></category>
		<category><![CDATA[Security]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3304</guid>
		<description><![CDATA[In my previous article on Parameter Tampering in ASP.NET MVC I focused on the general techniques of parameter tampering and defenses against it. In this article I will examine a specific type of parameter tampering which is often termed Mass Assignment. In most MVC web development frameworks (including ASP.NET MVC). Model binding works by assigning [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/asp-net-mvc-security-guarding-against-mass-assignment-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Protecting Against SQL Injection</title>
		<link>http://www.sql-server-performance.com/2012/protecting-against-sql-injection/</link>
		<comments>http://www.sql-server-performance.com/2012/protecting-against-sql-injection/#comments</comments>
		<pubDate>Thu, 04 Oct 2012 07:14:54 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[SQL Injection]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3262</guid>
		<description><![CDATA[Despite being so well understood, SQL Injection remains one of the most common vulnerabilities in web applications. What is SQL Injection Any SQL which is dynamically created has the potential for having malicious SQL injected into it. For example, the below code receives a querystring and adds it to a SQL select string which will [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/protecting-against-sql-injection/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Preventing Parameter Tampering in ASP.NET MVC</title>
		<link>http://www.sql-server-performance.com/2012/preventing-parameter-tampering-in-asp-net-mvc/</link>
		<comments>http://www.sql-server-performance.com/2012/preventing-parameter-tampering-in-asp-net-mvc/#comments</comments>
		<pubDate>Wed, 03 Oct 2012 05:17:04 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[Developer]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3246</guid>
		<description><![CDATA[Never trust data submitted from a web page is a core security concept for web development. When using an MVC framework, this statement takes on added relevance. MVC frameworks rely heavily on binding querystrings, route values and form values to in-code objects. Take for example the scenario where an authenticated user needs to update their [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/preventing-parameter-tampering-in-asp-net-mvc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Entity Framework Performance Optimization</title>
		<link>http://www.sql-server-performance.com/2012/entity-framework-performance-optimization/</link>
		<comments>http://www.sql-server-performance.com/2012/entity-framework-performance-optimization/#comments</comments>
		<pubDate>Tue, 24 Jul 2012 09:38:28 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3128</guid>
		<description><![CDATA[Query Tuning Minimise the Data Requested Minimising the data queried is a fundamental tenet of performance tuning for any method of data access. In querying a database using SQL, the below query should almost never make it into production : Select * From [Table] Instead, the query should specify the fields to be returned from [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/entity-framework-performance-optimization/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Using Entity Framework With An Existing SQL Server Database (Code Second)</title>
		<link>http://www.sql-server-performance.com/2012/entity-framework-existing-sql-server-database-code-second/</link>
		<comments>http://www.sql-server-performance.com/2012/entity-framework-existing-sql-server-database-code-second/#comments</comments>
		<pubDate>Mon, 23 Jul 2012 04:26:50 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3158</guid>
		<description><![CDATA[Entity Framework originally shipped with two modes &#8211; Model First which allowed for the entity model to be created using the designer UI and Database First which created the EF model from a database. EF 4.1 introduced Code-First development, enabling developers to simply generate the EF model and database directly from code. This method rapidly [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/entity-framework-existing-sql-server-database-code-second/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Entity Framework Gotchas</title>
		<link>http://www.sql-server-performance.com/2012/entity-framework-gotchas/</link>
		<comments>http://www.sql-server-performance.com/2012/entity-framework-gotchas/#comments</comments>
		<pubDate>Mon, 16 Jul 2012 06:23:21 +0000</pubDate>
		<dc:creator>Jude O'Kelly</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[EF]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2877</guid>
		<description><![CDATA[Entity Framework is fast becoming the default data access method for small to medium sized apps in .NET. Whilst it offers a lot of benefits in terms of productivity and security, working with EF is often very different from working with the standard ADO.NET data-access objects and poses several common issues or &#8216;gotchas&#8217;: Using Different [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/entity-framework-gotchas/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
