richardmgreen1 - Thursday, April 19, 2018 4:06 AM
No, don't need to restart.
Yes, that table is definitely too large. Every MAX pointer still takes 16 bytes. I have code that calcs roughly the max possible overhead bytes, and it returns this:
total_max_row_length data_length var_lengths bit_map general_row_overhead
9599 8465 1054 69 11
This might be overstated, if the 2-byte varchar length counter is in the overflow area when you force the overflow data there, but either way, it could be past 8060 bytes.
Basically you'll need to split this table into two tables, putting roughly half the column data into each one.
Btw, I wouldn't -- and didn't -- suggest running that code arbitrarily against all tables, it's not a generic solution.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.