July 7, 2011 at 2:18 pm
Comments posted to this topic are about the item Stairway to SQL Server Indexes: Step 13, Insert Update Delete
July 13, 2011 at 12:36 am
Arcticle has double header
February 29, 2012 at 5:38 am
You have a contradiction when you talks about page splits on inserts.
>>
Ascending Sequence:...Once a page becomes full, it stays full; resulting in little or no internal fragmentation.
Descending Sequence:...The internal fragmentation is the same as
the ascendingsequence scenario; at or near 100%.
<<
Either Ascending should be "at or near 100%" or Descending should be "little or no fragmentation".
------------
Buy the ticket, take the ride. -- Hunter S. Thompson
February 29, 2012 at 6:16 am
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.
"Keep Trying"
February 29, 2012 at 11:51 am
If a page contains ghosted records will it still split on insert?
July 7, 2012 at 11:38 am
There is a DML trigger defined on the table.
Can you please let me know if this in actually cause delete/insert for updarte? I couldnt see this behaviour.
GulliMeel
Finding top n Worst Performing queries[/url]
Improve the performance of Merge Join(special case)
How to Post Performance Problem -Gail Shaw[/url]
September 6, 2012 at 11:16 pm
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.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply