<?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; Developer</title>
	<atom:link href="http://www.sql-server-performance.com/category/articles/developer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Mon, 20 May 2013 03:15:15 +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>SQL Server Transactions and Locking –  Part 1</title>
		<link>http://www.sql-server-performance.com/2013/transactions-locking/</link>
		<comments>http://www.sql-server-performance.com/2013/transactions-locking/#comments</comments>
		<pubDate>Wed, 08 May 2013 04:25:48 +0000</pubDate>
		<dc:creator>Basit Farooq</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[locking]]></category>
		<category><![CDATA[transactions]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3636</guid>
		<description><![CDATA[In many situations, data modification requires several steps. For example, you may need to change the values &#8203;&#8203;in two separate tables. You can use transactions to complete these two operations as a unit, or if an error occurs, does not change any of the tables. Another key consideration is that most databases must be compatible [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/transactions-locking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Forwarding Pointers in Heaps</title>
		<link>http://www.sql-server-performance.com/2013/forwarding-pointers-in-heaps/</link>
		<comments>http://www.sql-server-performance.com/2013/forwarding-pointers-in-heaps/#comments</comments>
		<pubDate>Wed, 17 Apr 2013 00:58:31 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[Heaps]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[Pointers]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3620</guid>
		<description><![CDATA[When no clustered index is defined on a table, that table is said to be a Heap. Heaps are not ideal when it comes to performance but there are lots of instances where you have heaps.   Operations on heaps INSERT -  New rows can be placed in the first available page with sufficient space. [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/forwarding-pointers-in-heaps/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Configuring and Creating An AlwaysOn Availability Group in SQL Server 2012</title>
		<link>http://www.sql-server-performance.com/2013/configuring-creating-alwayson-availability-group-sql-server-2012/</link>
		<comments>http://www.sql-server-performance.com/2013/configuring-creating-alwayson-availability-group-sql-server-2012/#comments</comments>
		<pubDate>Tue, 26 Mar 2013 18:30:08 +0000</pubDate>
		<dc:creator>Arshad Ali</dc:creator>
				<category><![CDATA[Clustering]]></category>
		<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[AlwaysOn]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2842</guid>
		<description><![CDATA[In the previous article on AlwaysOn Availability Groups in SQL Server 2012, we looked at The Environmental Setup for An AlwaysOn Availability Group. In this article we turn our attention to the creation and configuration of the Availability Group. There are two primary steps to creating an AlwaysOn availability group which has to be done [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/configuring-creating-alwayson-availability-group-sql-server-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server 2012 AlwaysOn Availability Group Environmental Setup</title>
		<link>http://www.sql-server-performance.com/2013/sql-server-alwayson-availability-group-environmental-setup/</link>
		<comments>http://www.sql-server-performance.com/2013/sql-server-alwayson-availability-group-environmental-setup/#comments</comments>
		<pubDate>Wed, 20 Mar 2013 00:12:33 +0000</pubDate>
		<dc:creator>Arshad Ali</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[AlwaysOn]]></category>
		<category><![CDATA[Clustering]]></category>
		<category><![CDATA[high availability]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2833</guid>
		<description><![CDATA[Continuing from AlwaysOn Part 1 the series continues with a step-by-step guide to setting up the environment for an AlwaysOn availability group. In this article we will break down AlwaysOn environment preparation into three steps : Installation of SQL Server 2012 on each node/replica/server. Installation of the failover clustering feature on each node/replica/server. Creation of [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/sql-server-alwayson-availability-group-environmental-setup/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using Filtered Indexes to Improve Performance</title>
		<link>http://www.sql-server-performance.com/2013/sql-server-filtered-indexes-performance/</link>
		<comments>http://www.sql-server-performance.com/2013/sql-server-filtered-indexes-performance/#comments</comments>
		<pubDate>Tue, 12 Mar 2013 06:57:51 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[filtered index]]></category>
		<category><![CDATA[index]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3591</guid>
		<description><![CDATA[A Filtered Index is a new index type introduced in SQL Server 2008. In simple terms, rather than adding a non-clustered index to the entire table, you can add an index to a filtered data set. The syntax for creating a filtered index is : CREATE NONCLUSTERED INDEX &#60;Index_Name&#62; ON &#60;Table Name&#62;(&#60;Column(s)&#62;) WHERE &#60;Filter Condition&#62; [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/sql-server-filtered-indexes-performance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>Performance Impact of Using SELECT COUNT(*) In Queries</title>
		<link>http://www.sql-server-performance.com/2013/performance-select-count-queries/</link>
		<comments>http://www.sql-server-performance.com/2013/performance-select-count-queries/#comments</comments>
		<pubDate>Tue, 22 Jan 2013 03:17:08 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Count]]></category>
		<category><![CDATA[TSQL]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3545</guid>
		<description><![CDATA[I am not sure how this statement came into common usage, however, it seems to be regularly used by developers. Count(*) will use a table scan or Clustered index scan and so will eventually impair performance. In the case of a large table, a table scan or clustered index scan will impair your query performance, [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/performance-select-count-queries/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>SQL Server Performance Tuning &#8211; Index Tuning</title>
		<link>http://www.sql-server-performance.com/2013/sql-server-index-tuning/</link>
		<comments>http://www.sql-server-performance.com/2013/sql-server-index-tuning/#comments</comments>
		<pubDate>Wed, 09 Jan 2013 01:01:29 +0000</pubDate>
		<dc:creator>Shehap El-Nagar</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[T-SQL]]></category>
		<category><![CDATA[Tuning]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3457</guid>
		<description><![CDATA[In earlier installments of this series we looked at T-SQL Performance optimizations along with different T-SQL practices, we can now turn our attention to the second part of this series which is index Tuning In looking into Views we will break the article into two sections : Basic Index Tuning using DTA (Database Tuning Advisor) [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/sql-server-index-tuning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VARCHAR (MAX), NVARCHAR (MAX) and NTEXT Data Types</title>
		<link>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/</link>
		<comments>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/#comments</comments>
		<pubDate>Wed, 05 Dec 2012 05:15:12 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[ntext]]></category>
		<category><![CDATA[nvarchar]]></category>
		<category><![CDATA[text]]></category>
		<category><![CDATA[TSQL]]></category>
		<category><![CDATA[varchar]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3453</guid>
		<description><![CDATA[Despite NTEXT and TEXT being deprecated in SQL Server for some time they are still both used in production systems. In this article, I will briefly demonstrate the difference between a VARCHAR (MAX), NVARCHAR (MAX) and the NTEXT data types, and the impact on performance from using NTEXT/TEXT. Let’s create a table named Student using [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/varchar-max-nvarchar-max-ntext-data-types/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>SQL Server T-SQL Tuning &#8211; NOT IN and NOT Exists</title>
		<link>http://www.sql-server-performance.com/2012/sql-server-t-sql-tuning-not-in-and-not-exists/</link>
		<comments>http://www.sql-server-performance.com/2012/sql-server-t-sql-tuning-not-in-and-not-exists/#comments</comments>
		<pubDate>Sat, 01 Dec 2012 13:09:57 +0000</pubDate>
		<dc:creator>Shehap El-Nagar</dc:creator>
				<category><![CDATA[Developer]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[NOT Exists]]></category>
		<category><![CDATA[NOT IN]]></category>
		<category><![CDATA[TSQL]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3380</guid>
		<description><![CDATA[Following on from the previous TSQL performance tuning article in this series, we now focus on the important topic of T-SQL &#8220;Not IN&#8221; And &#8220;Not Exists &#8220; Not in and Not Exists commands : In some circumstances we will need to select/update/delete orphan data &#8211; that is data does not exists in the major table [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/sql-server-t-sql-tuning-not-in-and-not-exists/feed/</wfw:commentRss>
		<slash:comments>31</slash:comments>
		</item>
	</channel>
</rss>
