﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by David Durant  / Stairway to SQL Server Indexes: Step 13, Insert Update Delete / 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>Fri, 24 May 2013 05:59:15 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>great post.i read it through 1 to 15.but there is some mistake.for example,10th's list 2 is same as list one,which should be create table and load data instead of create view.and 15th,guildline,the explanation of why use include column is mistake.</description><pubDate>Thu, 06 Sep 2012 23:16:21 GMT</pubDate><dc:creator>xpboyzcx</dc:creator></item><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>[quote]There is a DML trigger defined on the table. [/quote]Can you please let me know if this in actually cause delete/insert for updarte? I couldnt see this behaviour.</description><pubDate>Sat, 07 Jul 2012 11:38:30 GMT</pubDate><dc:creator>Gullimeel</dc:creator></item><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>If a page contains ghosted records will it still split on insert?</description><pubDate>Wed, 29 Feb 2012 11:51:35 GMT</pubDate><dc:creator>colinallen@hsbc.com</dc:creator></item><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>I think all the author is trying to say is that in both the cases there will be little de-fragmentation. So overall fragmentation will be near to 100.</description><pubDate>Wed, 29 Feb 2012 06:16:21 GMT</pubDate><dc:creator>ChiragNS</dc:creator></item><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>You have a contradiction when you talks about page splits on inserts.&amp;gt;&amp;gt;Ascending Sequence:...Once a page becomes full, it stays full; resulting in little or no internal fragmentation.Descending Sequence:...The internal fragmentation[b] is the same as [/b]the ascendingsequence scenario; at or near 100%.&amp;lt;&amp;lt;Either Ascending should be "at or near 100%" or Descending should be "little or no fragmentation".</description><pubDate>Wed, 29 Feb 2012 05:38:48 GMT</pubDate><dc:creator>G Bryant McClellan</dc:creator></item><item><title>RE: Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>Arcticle has double header</description><pubDate>Wed, 13 Jul 2011 00:36:04 GMT</pubDate><dc:creator>dronusoid</dc:creator></item><item><title>Stairway to SQL Server Indexes: Step 13, Insert Update Delete</title><link>http://www.sqlservercentral.com/Forums/Topic1138527-2904-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Stairway+Series/72445/"&gt;Stairway to SQL Server Indexes: Step 13, Insert Update Delete&lt;/A&gt;[/B]</description><pubDate>Thu, 07 Jul 2011 14:18:16 GMT</pubDate><dc:creator>David Durant</dc:creator></item></channel></rss>