September 3, 2009 at 11:44 pm
For instance we have a table with 4 non-clustered indexes for each insert, delete and update operation it has to write additionally to the SQL Server memory 4 times when the record is updated. What if the update happens to be non-indexed field does it still need to write to the memory?
Regards........
September 4, 2009 at 8:26 am
Updating a non-indexed column should not affect any indexes.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 4, 2009 at 9:38 am
Thanks very much............
September 4, 2009 at 2:00 pm
if the column being updated causes a page split, it will affect the indexes.
The probability of survival is inversely proportional to the angle of arrival.
September 4, 2009 at 2:49 pm
I don't think a page split caused by an update to a non-indexed column will affect the size of a non-clustered index, check this blog post by Paul Randal. It MAY affect the performance of a NC index because of an extra IO, but the NC index will not have page split.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
September 6, 2009 at 5:45 am
so ...
1) any data write goes to the memory
2) during updating non-indexed column witch wasn't included by any index - there is no size growth/page split
3) during updating non-indexed column witch was included by nonclustered index - it is possible that the index may change
including column into indexes is available in sql 2005 and later
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply