Gail is correct and I didn't mean to imply that it was the cause of a row missing from an index. I meant it only as a bit of advice and my out of place comment of "and then you won't have such problems" was directed at the too-wide an index problem and not the post I quoted.
I also forgot to add that I'd like to see the precise code that makes you think that an index is missing a row as well as the code that creates the index. The reason being is just like Gail said. Unless there's some sort of latent problem with the SQL Server code itself (and that HAS happened and will happen again) or you do have some faulty hardware, what you're describing is impossible and that's why I'd like to see the exact code you used to determine a row is missing from the index and the code that created the index so that we can try to duplicate the problem (although it may still be a problem because I don't have a copy of 2005 anymore).
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems