ONLINE index rebuild adds one extra byte to non-clustered indexes

Question

Post reply

ONLINE index rebuild adds one extra byte to non-clustered indexes

Viewing 4 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Johan Bijnens SSC Guru Points: 135550 More actions · Answer 1

I'll put in a virtual pint :w00t:

Let's hope for the code mismatch, even if in both sql2005 as wel as 2008.

I'll vote on Connect !

Problem is, we cannot trace/dump the intermediate index during its online rebuild and the fase where they will have to run through the logs to update work in progress during the online rebuild operation.

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Paul White SSC Guru Points: 150468 More actions · Answer 2

ALZDBA (9/9/2009)
I'll vote on Connect !

Thanks very much! :w00t:

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

Paul White SSC Guru Points: 150468 More actions · Answer 3

A super fast response from Sunil Agarwal on Connect.

Sunil Agarwal
Thanks for contacting us. You will notice that with ONLINE, we are adding an extra byte at position 2 in the record. This extra byte is used internally for ONLINE build. This only happens for non clustered index.

The other 'mysterious byte' in the row turns out to be just a row header byte (though that's not in BOL either).

I guess that removing the 'extra byte' from the index row after the internal operation has finished would be just too expensive to do, and not worth the small gain. I'm happy with that 😎