﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / Clustered index update / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 21:21:19 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Clustered index update</title><link>http://www.sqlservercentral.com/Forums/Topic1059874-146-1.aspx</link><description>Thanks for all your replies</description><pubDate>Tue, 08 Feb 2011 08:47:21 GMT</pubDate><dc:creator>Matt-1034261</dc:creator></item><item><title>RE: Clustered index update</title><link>http://www.sqlservercentral.com/Forums/Topic1059874-146-1.aspx</link><description>Also, also, be cognizant of the fact that just becuase you have a high cost in an execution plan, doesn't mean that the process itself is very high cost. Execution plan costs are just estimates and do not represent measures that you can use to determine performance.</description><pubDate>Tue, 08 Feb 2011 07:31:30 GMT</pubDate><dc:creator>Grant Fritchey</dc:creator></item><item><title>RE: Clustered index update</title><link>http://www.sqlservercentral.com/Forums/Topic1059874-146-1.aspx</link><description>Also be aware that the execution plan adds up to 100%, so something will take up resources. If you have the index on fields that the update can use, then the resource usage should be minimal.</description><pubDate>Mon, 07 Feb 2011 13:33:56 GMT</pubDate><dc:creator>Steve Jones - SSC Editor</dc:creator></item><item><title>RE: Clustered index update</title><link>http://www.sqlservercentral.com/Forums/Topic1059874-146-1.aspx</link><description>The "clustered index" is, for all intents and purposes, the table itself.  I would expect that to the majority of the work on a simple update.In other words, this is normal and expected.You'll want to take a look at how clustered indexes work.  If you'll be administering or performance tuning, you'll need to know about them.</description><pubDate>Mon, 07 Feb 2011 13:21:44 GMT</pubDate><dc:creator>GSquared</dc:creator></item><item><title>Clustered index update</title><link>http://www.sqlservercentral.com/Forums/Topic1059874-146-1.aspx</link><description>HiOn our website when someone views a members image we update a field called visits which is just a counter that shows how many times an image has been viewed.The sql statement looks like this : -[code="sql"]update images set visits=visits+1 where (username=@username) AND (mykey=@mykey)[/code]However I have noticed that looking at the execution plan a clustered index update is taking place which is taking up 86%.Anyone know why this might be?ThanksMatt</description><pubDate>Mon, 07 Feb 2011 13:06:43 GMT</pubDate><dc:creator>Matt-1034261</dc:creator></item></channel></rss>