﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 Administration  / Non-Clustered index updates / 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 13:30:48 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Non-Clustered index updates</title><link>http://www.sqlservercentral.com/Forums/Topic1363813-1550-1.aspx</link><description>Absolutely. Has to be, otherwise the nonclustered indexes don't match the table (and that's called corruption). Could be more than that if there is an index on that column as the non-leaf levels may need updating too.</description><pubDate>Tue, 25 Sep 2012 04:18:28 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: Non-Clustered index updates</title><link>http://www.sqlservercentral.com/Forums/Topic1363813-1550-1.aspx</link><description>That is correct but how it will do? Say in our case TestTable if we update DeptID of any user then the actual data page of clustered index will be updated first (this is the only actual physical page), and question comes to Non-clustered will the Depid also update at the non-clustered leaf level?That means two updates at page levels?Thank you</description><pubDate>Tue, 25 Sep 2012 04:03:52 GMT</pubDate><dc:creator>SQL*</dc:creator></item><item><title>RE: Non-Clustered index updates</title><link>http://www.sqlservercentral.com/Forums/Topic1363813-1550-1.aspx</link><description>During the execution of the insert/update/delete always. A nonclustered index is never out of date.</description><pubDate>Tue, 25 Sep 2012 01:19:38 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>Non-Clustered index updates</title><link>http://www.sqlservercentral.com/Forums/Topic1363813-1550-1.aspx</link><description>Hi All,Basic question is: When does the non-clustered index update (when we do any updates on table)?We have created a non-clustered index, when we update the table's column which is the key of non-clustered index then the execution plan is showing only clustered index update. What about the non-clustered index update? How the non-clustered index key values modified?Include Column index:If we have a non-clustered index by including the columnEx: TestTable -- id int P.K, Name varchar(50), DeptID INTi have created non-clustered index on Name by including the DeptIDcreate index idx_nameon TestTable (Name) Include (Deptid)that means the non-clustered index leaf level pages contains DeptID also.My Question is when we update Deptid column of TestTable, how the non-clustered index leaflevel will be updated? Will this non-clustered index update? my execution plan is not showing the non-clustered update.Please find the attached scripts/execution plan of update statement.</description><pubDate>Tue, 25 Sep 2012 00:44:21 GMT</pubDate><dc:creator>SQL*</dc:creator></item></channel></rss>