Thanks John ... the explanation was great, but if you notice in my query, I'm casing 'IsParent' and 'ParentWorkOrderNo'. How would I go about adding this into the WITH?

Thanks

That works, thank you ... but can anyone explain why mine does not? It works perfect in 2005 ... this is driving me insane.

Yep, ad-hoc that would work great with a GO, but this is a piece of a stored proc ...

It would appear that it is parsing the SQL before hand and determining that the column does not yet exist ... this is truly got me at a loss.

ah ha, that was it ... good call.

Msg 8928, Level 16, State 1, Line 1

Object ID 1419152101, index ID 5, partition ID 72057594157858816, alloc unit ID 72057594172669952 (type In-row data):...

And just forget about any non-index statistics? No thanks.

Msg 601, Level 12, State 3, Line 1

Could not continue scan...

No, I'm testing locally against my own machine ...

Ok, I looked at each column that has a computed column, and none of them contain a double quote ... yet they all have single quotes for strings. I'm not...

Found it ... is_computed in sys.columns.

Ah yeah, good call ... so that got me out of the negatives. These numbers still don't add up to the 50gb growth, but I'd assume that rebuilding the entire...

I thought that all was done in the log ... wow, so even after the operation has completed, it won't release the space unless I shrink it?

Correct.

I don't use maintenance plans ...

I think this may have to do with the index being created with quoted identifier on ... perhaps the computed column has a double...

I think my biggest table in this database is 56gb.

The crazy thing is that sp_spaceused is reporting:

index_sizeunused

-2230440 KB-36888 KB

Negatives!? How is that possible?