I'm pretty sure the index always gets updated when rows are INSERTed, UPDATEd or DELETEd regardless of the setting, because it must or the database would lose track of rows in the table. What is not updated is statistics on any queries that use the table.
If you add the INDEX with STATISTICS_NORECOMPUTE = ON, then existing statistics would be retained for all impacted queries, impairing the optimizer's ability to utilize the new INDEX to improve a queries performance. With it OFF, then the statistics would be updated when the INDEX is added.
Someone else may be better equipped to explain this than me though.
While they're at it, why did MS have to use STATISTICS_NORECOMPUTE instead of STATISTICS_RECOMPUTE? The double negative drives me batty! :w00t:
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St