<?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>Thinknook &#187; SQL Optimisation</title>
	<atom:link href="http://thinknook.com/category/sql-server/sql-optimisation/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinknook.com</link>
	<description>Because the world needs another Business Intelligence blog!</description>
	<lastBuildDate>Tue, 03 Jun 2014 22:09:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.41</generator>
	<item>
		<title>In-Memory (Memory Optimized) Tables in SQL Server 2014</title>
		<link>http://thinknook.com/in-memory-memory-optimized-tables-and-oltp-with-sql-server-2014-2013-07-12/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=in-memory-memory-optimized-tables-and-oltp-with-sql-server-2014</link>
		<comments>http://thinknook.com/in-memory-memory-optimized-tables-and-oltp-with-sql-server-2014-2013-07-12/#comments</comments>
		<pubDate>Fri, 12 Jul 2013 01:32:29 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Development]]></category>
		<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[SQL Server DBA]]></category>
		<category><![CDATA[hekaton]]></category>
		<category><![CDATA[in-memory]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[memory tables]]></category>
		<category><![CDATA[memory-optimized]]></category>
		<category><![CDATA[sql 14]]></category>
		<category><![CDATA[sql 2014]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[statistics]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=1147</guid>
		<description><![CDATA[In-Memory storage technology finally make their debut appearance on the SQL Server 2014&#8217;s BI stack, with the creation of a proper memory optimized tables and stored procedures, unlike the Columnstore feature which offers a read-only memory optimized solution, that does not work overly well in a true transactional environment. In this post I hope to [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/in-memory-memory-optimized-tables-and-oltp-with-sql-server-2014-2013-07-12/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Rehashing SQL Server Hashing Algorithms for Large Text Fields</title>
		<link>http://thinknook.com/rehashing-sql-server-hashing-algorithms-for-large-text-fields-2013-03-23/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=rehashing-sql-server-hashing-algorithms-for-large-text-fields</link>
		<comments>http://thinknook.com/rehashing-sql-server-hashing-algorithms-for-large-text-fields-2013-03-23/#comments</comments>
		<pubDate>Sat, 23 Mar 2013 19:51:29 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[C#]]></category>
		<category><![CDATA[MS SQL Server]]></category>
		<category><![CDATA[SQL Development]]></category>
		<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[checksum]]></category>
		<category><![CDATA[fnv]]></category>
		<category><![CDATA[hash]]></category>
		<category><![CDATA[hash algorithms]]></category>
		<category><![CDATA[hashbytes]]></category>
		<category><![CDATA[md2]]></category>
		<category><![CDATA[md4]]></category>
		<category><![CDATA[md5]]></category>
		<category><![CDATA[sha1]]></category>
		<category><![CDATA[sha2]]></category>
		<category><![CDATA[sql]]></category>
		<category><![CDATA[sql server]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=1048</guid>
		<description><![CDATA[Hashing can be a very useful technique when dealing with the storage and look up of large text fields (say a table of URLs or Search Keywords), these fields will incur high resource utilization on any database engine if used directly in DML statements, in which they are either filtered by or aggregated on. Any index built on these [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/rehashing-sql-server-hashing-algorithms-for-large-text-fields-2013-03-23/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Locking Control and Transaction Isolation Levels</title>
		<link>http://thinknook.com/sql-server-locking-control-and-transaction-isolation-levels-2012-12-03/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sql-server-locking-control-and-transaction-isolation-levels</link>
		<comments>http://thinknook.com/sql-server-locking-control-and-transaction-isolation-levels-2012-12-03/#comments</comments>
		<pubDate>Mon, 03 Dec 2012 13:10:16 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[SQL Server DBA]]></category>
		<category><![CDATA[locking]]></category>
		<category><![CDATA[snapshot]]></category>
		<category><![CDATA[sql server]]></category>
		<category><![CDATA[transaction isolation]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=859</guid>
		<description><![CDATA[SQL Server uses two methods to ensure transactional consistency and protects the data that is being accessed, these are Locks and Row-Versioning, these methods ensure that you manage your data concurrency effectively by specifying the level of access other transactions have to the data being processed, the game here is to balance either resources or data integrity against [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/sql-server-locking-control-and-transaction-isolation-levels-2012-12-03/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identify SQL Server Object Using Resource Page ID</title>
		<link>http://thinknook.com/identify-sql-server-object-using-resource-page-id-2012-06-19/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=identify-sql-server-object-using-resource-page-id</link>
		<comments>http://thinknook.com/identify-sql-server-object-using-resource-page-id-2012-06-19/#comments</comments>
		<pubDate>Tue, 19 Jun 2012 13:35:28 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[SQL Server DBA]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=619</guid>
		<description><![CDATA[Sometimes one might like to identify a particular SQL Server resource using the Page ID this resource is under, you might notice a Page ID sometimes on the Activity Monitor page under the Wait Resource column, if a certain query is waiting on a particular resource, some DMVs will reference Page IDs as well as [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/identify-sql-server-object-using-resource-page-id-2012-06-19/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SQL Server Query Execution Plan from Cache</title>
		<link>http://thinknook.com/sql-server-query-execution-plan-from-cache-2012-05-29/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sql-server-query-execution-plan-from-cache</link>
		<comments>http://thinknook.com/sql-server-query-execution-plan-from-cache-2012-05-29/#comments</comments>
		<pubDate>Tue, 29 May 2012 13:46:18 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[SQL Server DBA]]></category>
		<category><![CDATA[T-SQL]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=600</guid>
		<description><![CDATA[There are many ways to obtain the execution plan of a SQL Server query, each of which serves a particular purpose, for example if you can run a query easily, then the best way to get an execution plan is to simply enable the execution plan (either through SSMS or SETting the correct session option), [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/sql-server-query-execution-plan-from-cache-2012-05-29/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Optimizing SQL Server Wait Types</title>
		<link>http://thinknook.com/optimizing-sql-server-wait-types-2012-03-26/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=optimizing-sql-server-wait-types</link>
		<comments>http://thinknook.com/optimizing-sql-server-wait-types-2012-03-26/#comments</comments>
		<pubDate>Mon, 26 Mar 2012 09:00:51 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=547</guid>
		<description><![CDATA[Optimizing SQL Server&#8217;s Wait Types can be a daunting task, there are so many interdependencies to account for, and most of the time optimising a Wait Type could mean sacrificing other system resources (such as disk space) or SQL tasks (such as INSERTs on the underlying table through index creation). This post will give you [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/optimizing-sql-server-wait-types-2012-03-26/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Merge Join &#8211; SQL Server Graphical Execution Plan</title>
		<link>http://thinknook.com/merge-join-sql-server-graphical-execution-plan-2012-03-25/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=merge-join-sql-server-graphical-execution-plan</link>
		<comments>http://thinknook.com/merge-join-sql-server-graphical-execution-plan-2012-03-25/#comments</comments>
		<pubDate>Sun, 25 Mar 2012 10:00:45 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=526</guid>
		<description><![CDATA[Merge Join can be a very fast join operation, although it has some underlying behavior that could dramatically increase the over-all cost this operator has on the query execution plan. In this post I will go through how SQL Server utilizes the Merge Join operator for performing logical join operations, as well as the different [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/merge-join-sql-server-graphical-execution-plan-2012-03-25/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nested Loops Join &#8211; SQL Server Graphical Execution Plan</title>
		<link>http://thinknook.com/nested-loop-join-sql-server-graphical-execution-plan-2012-03-25/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=nested-loop-join-sql-server-graphical-execution-plan</link>
		<comments>http://thinknook.com/nested-loop-join-sql-server-graphical-execution-plan-2012-03-25/#comments</comments>
		<pubDate>Sun, 25 Mar 2012 08:00:42 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=524</guid>
		<description><![CDATA[Nested Loops Join operator (represented by an inner and an outer looping arrows in SQL Server&#8217;s Graphical Execution Plan) is used by SQL Server to join together two tables or indexes, this is generally an efficient operator, and superior to Hash or Merge Joins when operating on small data-sets. This post will goes through why [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/nested-loop-join-sql-server-graphical-execution-plan-2012-03-25/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hash Match &#8211; SQL Server Graphical Execution Plan</title>
		<link>http://thinknook.com/hash-match-sql-server-graphical-execution-plan-2012-03-25/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=hash-match-sql-server-graphical-execution-plan</link>
		<comments>http://thinknook.com/hash-match-sql-server-graphical-execution-plan-2012-03-25/#comments</comments>
		<pubDate>Sat, 24 Mar 2012 23:02:19 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=522</guid>
		<description><![CDATA[Hash Match is a strategy used by SQL Server to join two tables together using the Hash Bucket and Hashing Algorithm approach, this approach is taken when joining tables or aggregating rows. In this post we will go through what is a Hash Match, what are the types of Hash Match, why does SQL Server [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/hash-match-sql-server-graphical-execution-plan-2012-03-25/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SQL Server Query Index Statistics</title>
		<link>http://thinknook.com/sql-server-query-index-statistics-2012-03-19/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=sql-server-query-index-statistics</link>
		<comments>http://thinknook.com/sql-server-query-index-statistics-2012-03-19/#comments</comments>
		<pubDate>Mon, 19 Mar 2012 18:26:39 +0000</pubDate>
		<dc:creator><![CDATA[Links Naji]]></dc:creator>
				<category><![CDATA[SQL Optimisation]]></category>
		<category><![CDATA[SQL Server DBA]]></category>

		<guid isPermaLink="false">http://thinknook.com/?p=511</guid>
		<description><![CDATA[This post goes through the SQL Server DBCC command which deals with displaying the actual underlying statistics to a particular SQL Server index. Statistics are vital for optimising SQL query performance, SQL Server uses index statistics of all the underlying tables when trying to satisfy the processing of a query, ensuring that your statistics are [&#8230;]]]></description>
		<wfw:commentRss>http://thinknook.com/sql-server-query-index-statistics-2012-03-19/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.w3-edge.com/products/


Served from: thinknook.com @ 2026-04-15 00:28:41 by W3 Total Cache
-->