<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Creating clustered index on exiting table</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/creating-clustered-index-on-exiting-table/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/creating-clustered-index-on-exiting-table/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 13:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: dataismypassion</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/creating-clustered-index-on-exiting-table/#comment-106714</link>
		<dc:creator>dataismypassion</dc:creator>
		<pubDate>Fri, 13 Apr 2012 16:08:53 +0000</pubDate>
		<guid isPermaLink="false">#comment-106714</guid>
		<description><![CDATA[I have to believe the column(s) that will be target of your primary key has data that is unique. If that is the case can you live with creating a non-clustered unique index on the column(s) ? If one of the purposes of wanting to create a primary key in the first place is to ensure row uniqueness then you will have satisfied your condition. Even if your reason is to improve performance, you will have created an index that will be the basis for retrieving data rather than retrieving from the heap. 
You may also want to check if your tempdb is constrained on max size. Index creation sometimes use tempdb.]]></description>
		<content:encoded><![CDATA[<p>I have to believe the column(s) that will be target of your primary key has data that is unique. If that is the case can you live with creating a non-clustered unique index on the column(s) ? If one of the purposes of wanting to create a primary key in the first place is to ensure row uniqueness then you will have satisfied your condition. Even if your reason is to improve performance, you will have created an index that will be the basis for retrieving data rather than retrieving from the heap.<br />
You may also want to check if your tempdb is constrained on max size. Index creation sometimes use tempdb.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.041 seconds using memcached
Object Caching 266/272 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-19 14:31:30 -->